25 Sep, 2015 Blogs
By Brad Brech, Distinguished Engineer, IBM Power Systems Solutions
Suppose you’re a game developer with a release coming up. If things go well, your user base could go from zero to hundreds of thousands in no time. And these gamers expect your app to capture and store their data, so the game always knows who’s playing and their progress in the game, no matter where they log in. You’re implementing an underlying database to serve these needs.
Oh—and you’ve got to do that without adding costly DRAM to existing systems, and without much of a budget to build a brand-new large shared memory or distributed multi-node database solution. Don’t forget that you can’t let your performance get bogged down with IO latency from a traditionally attached flash storage array.
More and more, companies are choosing NoSQL over traditional relational databases. NoSQL offers simple data models, scalability, and exceptionally speedy access to in-memory data. Of particular interest to companies running complex workloads is NoSQL’s high availability for key value stores (KVS) like Redis and MemcacheDB, document stores such as mongoDB and couchDB, and column stores Cassandra and BigTable.
NoSQL isn’t headache-free.
Running NoSQL workloads fast enough to get actionable insights from them is expensive and complex. That requires your business either to invest heavily in a shared-memory system or to set up a multi-node networked solution that adds complexity and latency when accessing your valuable data.
Back to our game developer and their demanding gamers. As the world moves to the cloud, developers need to offer users rapid access to online content, often tagged with metadata. Metadata needs low response times as it is constantly being accessed by users. NoSQL provides flexibility for content-driven applications to not only provide fast access to data but also store diverse data sets. That makes our game developer an excellent candidate for using CAPI-attached Flash to power a NoSQL database.
Here’s where CAPI comes in. Because CAPI allows you to attach devices with memory coherency at incredibly low latency, you can use CAPI to affix flash storage that functions more like extended block system memory for larger, faster NoSQL. Coming together, OpenPOWER Foundation technology innovators including Redis Labs, Canonical, and IBM created this brilliant new deployment model, and they built Data Engine for NoSQL—one of the first commercially available CAPI solutions.
CAPI-attached flash enables great things. By CAPI-attaching a 56 TB flash storage array to the POWER8 CPU via an FPGA, the application gets direct access to a large flash array with reduced I/O latency and overhead compared to standard I/O-attached flash. End-users can:
- Create a fast path to a vast store of memory
- Reduce latency by cutting the number of code instructions to retrieve data from 20,000 to as low as 2000, by eliminating I/O overhead1
- Increase performance by increasing bandwidth by up to 5X on a per-thread basis1
- Lower deployment costs by 3X through massive infrastructure consolidation2
- Cut TCO with infrastructure consolidation by shrinking the number of nodes needed from 24 to 12
Get Started with Data Engine for NoSQL
Getting started is easy, and our goal is to provide you with the resources you need to begin. This living list will continue to evolve as we provide you with more guidance, information, and use cases, so keep coming back to be sure you can stay up to date.
Learn more about the Data Engine for NoSQL:
Deploy Data Engine for NoSQL:
- Contact IBM about Data Engine for NoSQL to build the Data Engine for NoSQL configuration for you
- Get community support for your solutions and share results with your peers on the CAPI Developer Community
- Reach out to the OpenPOWER Foundation community on Twitter, Facebook, and LinkedIn along the way
Keep coming to see blog posts from IBM and other OpenPOWER Foundation partners on how you can use CAPI to accelerate computing, networking and storage.
- CAPI Series 1: Accelerating Business Applications in the Data-Driven Enterprise with CAPI
- CAPI Series 3: Interconnect Your Future with Mellanox 100Gb EDR Interconnects and CAPI
- CAPI Series 4: Accelerating Key-value Stores (KVS) with FPGAs and OpenPOWER
About Brad Brech
Brad Brech is a Distinguished Engineer and the CTO of POWER Solutions in the IBM Systems Division. He is currently focused on POWER and OpenPOWER and solutions and is the Chief Engineer for the CAPI attached Flash solution enabler. His responsibilities include technical strategy, solution identification, and working delivery strategies with solutions teams. Brad is an IBM Distinguished Engineer, a member of the IBM Academy of Technology and past Board member of The Green Grid.
Based on performance analysis comparing typical I/O Model flow (PCIe) to CAPI Attached Coherent Model flow.
 Based on competitive system configuration cost comparisons by IBM and Redis Labs.