« What is d178021a17b9c8800d8f45da53b3bd04? | Main | BigMemory Explained a bit... »
September 14, 2010
OK...so the news is out on BigMemory
posted by ari
BigMemory == d178021a17b9c8800d8f45da53b3bd04
How? that MD5 sum is of the integer number value for 256GB. 256GB is the maximum size of cache we had tested up to the time Greg Luck and I decided to start this little campaign. Since then we have gone past 350GB. But ah well. 350GB is a HUGE cache to load in a single JVM, without any full GC pauses and without any disk I/O (swap / flush to disk), and without any C / C++ hacks or weak reference tricks or what have you.
I will blog more about the value but for now alls [sic] you need to know is that we can load hundreds of gigabytes of cached data into a JVM without affecting GC at all. And, we can do it inside Ehcache and inside Terracotta servers. That's right. Both Ehcache and Terracotta transparently offer off-heap in-process storage for their cache data. Guess what else...that makes our server nearly pauseless.
More later on how to make a tiered storage system between heap, off-heap, local disk, and Terracotta arrays that let's you balance performance vs. offload and scale up vs. scale out!
--Ari
Trackback Pings
TrackBack URL for this entry:
http://blog.terracottatech.com/cgi-bin/mt/mt-tb.cgi/107
Comments
great news! look forward to hearing more.
Posted by: Peter Lin at September 14, 2010 5:15 PM
I was wondering if you ever considered changing the layout of your blog? Its very well written; I love what youve got to say. But maybe you could a little more in the way of content so people could connect with it better. Youve got an awful lot of text for only having one or two images. Maybe you could space it out better?
Posted by: Frankie Herbam at September 15, 2010 9:54 PM