Archive for the 'Benchmarks' Category

Next Page »

You want it Fast or Super Fast? – The IB, 10GbE , GigE Benchmark

November 16th, 2008

With the current global financial meltdown, the ability to effectively compete becomes essential. Faster data access and sharing are critical for business success. Speed is critical for beating the competition, translating into a need for better latency.
With MW products this means the ability to push your data from the client end point into the clustered [...]

Scaling the Web Layer – The Web Container Benchmark

November 7th, 2008

We have been working for the past few days on building a benchmark for our new web containers and its built-in integration with the apache load balancer.
The benchmark was running on Amazon EC2/EBS cloud and was deployed using our new web based cloud tools. The benchmark goal is to measure the scalability of the [...]

Memory Capacity Planning - The Footprint Benchmark

October 7th, 2008

The goal of this benchmark is to measure the memory footprint of the indexes the space maintains to boost read/take operations when searching for matching objects.
This should help users to plan the amount of memory to allocate when doing their capacity planning prior deploying the application. 

See blow the final Conclusions and the detailed report:
- [...]

How to Implement my Processor? - The Polling Container Benchmark

October 3rd, 2008

When implementing SBA application one of the first artifacts you need to implement would be a “processor”.
The processor would be the core of the system. It will consume incoming data, digest it and come up with some output result.  You can think about this processor as a subscriber listening for incoming messages sent into [...]

Write Latency Benchmark

September 26th, 2008

This post will focus on the Write latency benchmark.
This benchmark is relevant mostly for trading applications that are required to submit a request into the backend system as fast as they can. The goal of this benchmark is to understand how much time it takes for a single write operation done by a single remote [...]

Next Page »