I'm actually more interested in the "elastic memory" bit: http://www.azulsystems.com/products/zing/elastic-memory http://www.azulsystems.com/products/zing/elast

I'm actually more interested in the "elastic memory" bit: http://www.azulsystems.com/products/zing/elastic-memory http://www.azulsystems.com/products/zing/elastic-memory When I used to work with JVM's all day I was always frustrated about having to decide how big a maximum heap for a given app would be. We had some xml processing tasks that almost never used much memory but every now and then would need tons. It was one part I couldn't thin-provision. Am I right in interpreting this as shipping the JVM work off to a dedicated appliance-like server? Does that mean the memory profile on the appliance is the one that can be thin-provisioned? Heap size tuning is one of those things that made me hate the JVM.