In tests run at Solid Data, kdb logged 5,000 transactions per second on a Sun Solaris system and 1,000 fully synchronous transactions per second on a Microsoft Windows 2000 system. The companies said that the Solid Data file cache replaces the typical magnetic disks used on these systems, which limit synchronous commits to 100 transactions per second.
Solid Data tested kdb transaction performance on a Sun E-450 server with four 400 Mhz CPUs and 512 MB of main memory. The Windows test was run on a Pentium 4, 1.8 GHz CPU with 512 MB DRAM.
According to the companies, current kdb customers are processing thousands of database updates per second, compensating for disk limitations by using kdb bulk updates to log transactions. With the Solid Data file cache, bulk logging can be reduced or eliminated altogether.
"Transaction logging performance is essential to financial firms that must ensure the reliability of larger volumes of transactions, for example in e-commerce," said Arthur Whitney, Kx Systems CTO. "By adding a Solid Data file cache to either a Windows or Solaris system, our kdb customers can confidently scale to handle more transactions faster, while ensuring transaction reliability and maintaining the cost-effectiveness of their desktop or midrange hardware."
"Kdb and Solid Data deliver accelerated performance without risk to transaction reliability," said Wade Tuma, founder and CEO of Solid Data Systems. "By delivering transaction commits at the speed of main memory, and with the persistence of disk storage, Solid Data helps kdb customers achieve high transaction rates while ensuring persistent capture of every transaction. Also, by eliminating mechanical disk latency, Solid Data file cache increases server efficiency and CPU utilization, enabling customers to lower their per-transaction costs."
For more information, visit the Kx web site at www.kx.com.