Friday, July 18, 2008

ThumbCached - Distributed caching and storing system for small binary file/data

About

ThumbCached is a simple, high-performance, distributed caching and storing system for small file/data. It's commonly used to store large number of non-critical and small capacity and read frequently binary file or data, such as image thumbnails and user custom head icons on web site.

Features

  • Use two large files to store a large number of small data files, it can save disk space that the lots of small files wasted, also it’s simple to move and backup data.
  • Server and applications can be distributed in different servers, and multiple applications can also access the same server.
  • Built-in data caching system, it can enhance the access speed of data that frequently visits.
  • using standard HTTP protocol, kinds of programming languages (such as ASP.Net, PHP, etc.)
  • can use the existing components to access the service.
  • Use a “key” to access the file/data information and binary content, needn’t have to remember the path and file name, it can simplify the programming.
  • One server can open several storage units, different types of data (such as user custom head icons and image thumbnails) can stored separately.
  • Use asynchronous socket to provide high-performance.
    Service protocol ThumbCached using standard HTTP protocol to communicate with applications, it contains add/update, fetch and delete operations. The operation target is call “block” (a block contains a “key”, last modified time, binary data content), the “key” is a string that made up with letters and
    numbers, for example:"item001", "23A8F001C".

Checkout the following link for more information: http://www.domstorage.com

Wednesday, July 16, 2008

Debugging ASP.NET on a Production Server 101

Very good information about Debugging can be found at the following article: Debugging ASP.NET on a Production Server 101

Tuesday, July 08, 2008

triage bugs ...

today I found an interesting post about bugs and how people triage bugs:

Wil Shipley has written it down, in his blog post: "Pimp My Code, Part 15: The Greatest Bug of All" the following ordering which I totally agree with how bugs should be triage:

  • Data-loss bugs
  • Unavoidable crashers
  • Functionality-blocking bugs
  • Avoidable crashers
  • Avoidable bugs
  • Misfeatures
  • Performance issues
  • Feature suggestions
  • UI feedback

Monday, July 07, 2008

Oracle Error: ORA-00054 - resource busy and acquire with NOWAIT

Today I tried to create an INDEX over 2 columns where one of them were already indexed. After receiving the error ORA-00054 - resource busy and acquire with NOWAIT I needed some time that this is because of previous used INDEX.

Previously used index:
CREATE INDEX index_name ON table_name
(
column_name ASC
)
/

wanted to change it to the following:
CREATE INDEX index_name ON table_name
(
column_name1,column_name2
)
/

all I needed to do were to delete previous INDEX and then it run fine - maybe this is not at any scenario correctly to do but for my case it worked out.

Thursday, July 03, 2008

Measure HTTP Request with a HTTP Module

while I was working for a demo I needed to demonstrate differences between requests which are hitting Database and those requests which were hitting Shared Cache.

I found an article from Phil Hacked which solved all my needs. You can find the article over here.

Shared Cache - .Net Caching made easy

All information about Shared Cache is available here: http://www.sharedcache.com/. Its free and easy to use, we provide all sources at codeplex.

Facebook Badge