Welcome to MSDN Blogs Sign in | Join | Help

April 2009 - Posts

The dreaded error - Cache::Get: The request timed out
Sometimes you see this error in the Get calls and this can freak out people. There are a few reasons why this error may come. Internally we have a 15second timeout for calls (either Get or Put) .So if are not able to satisfy the request within that time, Read More...
More performance numbers
Anshul ran some more numbers to see the max throughput and latency that we have observed with CTP3. Here are some numbers to share. Note that these are the max throughput numbers and latencies observed at those values. If you reduce the throughput, then Read More...
Pushing Client Performance
You can increase the number of clients to increase the cache throughput. But sometimes if you want to have smaller set of clients and increase throughput, a trick is to use multiple DataCacheFactory instances. The DataCacheFactory instance creates a connection Read More...
Regions and high Availability
When talking to some customers and partners, there was some confusion regarding regions and high availability. There is a assumption that if you use regions you will not get High Availability. That is not correct - High Availability is orthogonal to whether Read More...
Announcing Velocity CTP3 !
Velocity Team is happy to announce release of Microsoft project code named "Velocity" CTP3 For community technology preview 3 (CTP3), Microsoft project code named "Velocity" offers several enhancements and revised APIs. The enhancements include cache Read More...
Performance!
In my MIX talk I told that for 2k reads, we take 3ms. It is actually the case under load where the servers are straining. Here is a latest performance shot that we got with the CTP3 bits. Bulk APIs: Note that these numbers are without any bulk operations. Read More...
Page view tracker