Hardware Considerations and Performance Metrics

By Jonathan Ring, President and Founder, Caringo
Date: March 2010

Abstract

CAStor was designed to deliver performance to meet the demands of small files in terms of transactions per second as well as large files measured in megabytes per second. The results of performance testing presented in this paper demonstrate CAStor's unique capability to provide throughput for both. It can addresses small file storage and archiving to meet requirements of the most demanding environments, e.g. archiving e-mail messages on the order of hundreds of thousands a day. CAStor also provides the performance needed for large files such as health images, video and other types of content that require hundreds of megabytes per second of bandwidth.

CAStor provides the performance needed for active content and improves as the cluster grows in size because it takes advantage of the added processing power of new nodes. By leveraging a software-only approach and being able to run on standard x86 hardware, CAStor also takes advantage of advancements in processor technology to improve performance. The throughput it delivers allows it to be used as primary storage for content of varying sizes, in the same cluster, and includes all the functionality required for archiving content to meet compliance and governance mandates. With CAStor, there is no need to separate active and archive content onto separate storage tiers.






  * All fields required