All you really need to know is that the CaptiveSAN network developed by Aperion removed all of the legacy storage and networking infrastructure, thereby removing all of the performance starving latency inherent in today’s SAN. We hate to say it, because it’s so overused, but SAN 2.0 is here to stay, and only Apeiron has it.
Unlike other SAN implementations where unneeded storage controllers, either hardware or software, as well as unnecessary, latency filled, and sometimes costly, networking protocols and hardware exist, the CaptiveSAN utilizes a novel lightweight storage protocol embedded on an FPGA enabled HBA to quickly and effortlessly pass data to the NVMe storage array in tact, and with a mere 3µs added latency, each and every 24 drive NVMe SAN looks and acts as if it is server captive flash. You heard that correct, each array looks to the application and the CPU as if it is a SAN in the server, exactly what Splunk was originally designed to see, server captive flash. In fact by utilizing all 8 lanes of the PCIe bus, the only provider that does, the CaptiveSAN in fact looks faster than server captive flash storage.
By removing all of the IO blocking infrastructure, CaptiveSAN achieves performance metrics that the other vendors will never be able to touch. A true linear scaling 18.4 million IOPS, 96GBSec, near-zero latency, 720TB in a 2U array. You can add as many CaptiveSAN NVMe arrays and the performance just grows in a true linear scaling fashion.
End result? 1.2TB-2.5TB of ingest per indexer per day all while running the full set of Splunk ES queries. In a day and age when most platforms talk about ingest rates in the 80-300GB range, this is a true game changer. Reduce your TCO and footprint and lose the sprawl and performance challenges found with your scale-out and tradition SAN architectures.
When it comes to Splunk performance and tuning as well as dealing with unforeseen challenges and issues that arise throughout the course of a Splunk deployment, inevitably there is one factor that is almost always at the root of everything, too much latency. In fact statistics show that over 80% of any Splunk Engineer’s time is spent dealing with issues and performance tuning in an attempt to deliver on the promise of Splunk enabled big data analytics. 80%, really? In any other discipline this would be untenable at best, and it should be when it comes to Splunk. There is one reason that so many engineers and managers are trying to figure out why they can’t actually ingest and analyze the amount of data needed to make key business decisions, latency in hardware networking stack as well as in the storage protocol and enablement stack. One can talk about IOPS, one can talk about bandwidth and throughput, but without a perspective on your true latency as it exists in your deployment, there is no perspective on the other benchmarks, it’s all about latency, and too much of it. That’s where Apeiron comes in.
Apeiron’s patented technology removes the legacy storage complex, and along with it, all of the application starving latency inherent within. The novel CaptiveSAN network, based on a lightweight hardened layer two ethernet (hardware only) driver with transport delivered across the most cost effective 40100 GBSec ethernet infrastructure, utilizes a minuscule 4B encapsulation in the process of moving data packets intact, completely addressing current latency, capacity, bandwidth, and performance constraints.
Storage in a headless state with CaptiveSAN, allows for the unfettered transfer of data in it’s native NVMe format without the payload present in current technology, exponentially reducing latency, while linearly scaling performance in what is already the world’s fastest and most scalable storage network. 18.4 + Million IOPS, 96GBSec bandwidth and 720TB per 2U chassis, with an unheard of 1.5-3.0 µS of added latency. Apeiron’s CaptiveSAN is so fast and with so little latency, that as a SAN, it actually appears to the application and server as captive DAS storage, the only of it’s kind. CaptiveSAN blends the best of SAN, Scale-out, and Hyper-Converged technologies with up to an 80% reduction in footprint and cost. Unthinkable, but true. Unlock those IOPS and gain access to every last drop of your bandwidth by removing the latency bottleneck. Apeiron’s near-zero latency CaptiveSAN solution is the missing piece to your splunk issues and challenges.
CaptiveSAN can help you mitigate and remove completely your Splunk challenges and performance issues. Flat out, nobody can touch the Aperion Splunk Appliance performance benchmarks in both optimal and real world application showdowns.
Bottomline, we have removed the IO bottleneck entirely and have created an environment whereby now, the application and the CPU are the bottleneck, get every last drop of performance, if you want more, that’s Intel’s problem to solve!
*Industry averages for Splunk> indexers is 100GB-300GB per indexer per day, and 70-80GB per indexer per day with standard Splunk> ES queries running concurrently.
Call Aperion today and Let CaptiveSAN put some spunk in your Splunk. 800-701-0243
We know you're all about big data and you want it fast, so we provided some about our ADS platform in the downloads below. Take a look, see what everyone is talking about, then give us a call so we can help you too. 18.4 million IOPS in 2U. Damn that’s fast.
