Zing has completely solved the garbage collection problem for us. We no longer need to concern ourselves with tuning the garbage collector or coding around it. This has saved us an enormous amount in terms of potential opportunity cost and allows us to spend more time on the business problems that really matter. Not having to butcher our code to make it garbage free has probably also helped us to retain a high level of productivity and a low level of defects.

We use it on highly visible applications, with application characteristics described above.

We use the Zing JVM to deliver Solr search capabilities to our clients. Without it, we would need a team of full-time engineers to continually shard and re-shard the indices so that small heaps are used to avoid pausing during garbage collection.

As we provide real-time, low-latency trading solutions, any 'pause' in the application flow can cause serious financial risks to our customers. We used to spend numerous hours tuning each release, and then each customer site, in order to minimize the length of pauses in the standard Java runtime. With Zing, we've now been able to re-allocate those tuning resources to general product development.

It has made it possible to spend time on developing new functions rather than optimizing old ones.