3 posts • joined 21 Apr 2012
I was wondering how it Kaminario could have possibly come up with an 'architecture' to make DRAM go thousands of times slower than it should. 3.4 milliseconds? That's ridiculous.
I looked at the benchmark docs...this thing is nothing but a rack full of forty-seven Dell server blades (cheapest available) connected to a FC SAN, with RAMdisk software, software RAID and an APC UPS to make it "non-volatile". Oh yeah, and a 1,900% markup piled on for good measure.
No, really. I'm not kidding.
So what? Anyone can slap this together with off-the-shelf parts in an hour...
Take a Intel E7 box off the shelf (IBM x3850 X5 is nice), load it with DRAM and RAMdisk software (e.g. SuperSpeed) and voila, you have up to 3TB of DRAM-speed disk...from a real vendor...with real support...for 1/3rd the price.
FYI, this is what SAP uses for their HANA in-memory database.
Explanation of Scale-In
Scale-in relates to elasticity. It's a concept that's been around a few years, and it's actually quite relevant to IBM's new systems, although not at all in the way their marketing folks have spun it.
Tinyurl for IBM link:
And there's a very nice picture here (Fig. 5):
- Vid Antarctic ice THICKER than first feared – penguin-bot boffins
- Hi-torque tank engines: EXTREME car hacking with The Register
- Review What's MISSING on Amazon Fire Phone... and why it WON'T set the world alight
- Product round-up Trousers down for six of the best affordable Androids
- Antique Code Show World of Warcraft then and now: From Orcs and Humans to Warlords of Draenor