Is $1,500,000 enough for a 1.0 release?

June 11, 2012 by Priit Potter

We in the Plumbr team decided that it is. Over the last few months in beta our customers have solved more than 200 memory leaks with the help of Plumbr.

200 leaks sounds cool, but how does it translate to money? You cannot force a leak to go away by just throwing piles of cash towards it. Instead of spending cash you spend time. A lot of time –  a memory leak in a decently sized enterprise application takes around three man weeks to solve. This includes the operations’ and developers’ collective time for hunting and solving the leak, some QA time for regression testing, and some management time for communication and release coordination. Of course, the actual costs vary in a very large scale, but this is what we currently can estimate based upon the initial customer feedback.

Three man-weeks might not sound awfully lot, but translate this into cash and things start to look a bit more sour. Quoting Fred Wilson - “A good rule of thumb is multiply the number of people on the team by $10k to get the monthly burn”. Ouch. This three weeks now looks more like a $7,500.

If we now apply some hardcore math and multiply the 200 (number of leaks found by Plumbr) by $7,500 (average cost to solve a leak) we can confidently say we have saved at least $1,500,000 to our early customers. This looked impressive, and as we didn’t have any major bugs open either, we decided to step ahead and call ourselves production quality alias 1.0.

Along the lines we also worked out the initial pricing model. The use of Plumbr is still free and we do not expect you to pay a dime before we have proven our value. You are only asked to pay when Plumbr detects a leak in your application. Plumbr notifies you of the existence of the memory leak, but to find out what is leaking and how to fix it, we ask you to fill in the credit card details (you can do this only once if you buy a subscription).

How much do we charge? A lot less than the $7,500 you’d spend trying to solve the issue on your own. 1/30 of it seemed like a fair amount for a start, so that’s what we are now charging you for the report.But now – go ahead, download Plumbr, attach it to your application and be secured – no more memory leaks and sleepless nights hunting them down!

Can't figure out what causes your OutOfMemoryError? Read more

ADD COMMENT

COMMENTS

Oh boy, no idea how we let that slip in. There were many people re-quoting us, and nobody noticed :( nnFixed it now, thanks!

Priit Potter

Can't figure out what causes your OutOfMemoryError? Read more

Latest
Recommended
You cannot predict the way you die
When debugging a situation where systems are failing due to the lack of resources, you can no longer count on anything. Seemingly unrelated changes can trigger completely different messages and control flows within the JVM. Read more
Tuning GC - it does not have to be that hard
Solving GC pauses is a complex task. If you do not believe our words, check out the recent LinkedIn experience in garbage collection optimization. It is a complex and tedious task, so we are glad to report we have a whole lot simpler solution in mind Read more
Building a nirvana
We have invested a lot into our continuous integration / delivery infrastructure. As of now we can say that the Jenkins-orchestrated gang consisting of Ansible, Vagrant, Gradle, LiveRebel and TestNG is something an engineer can call a nirvana. Read more
Creative way to handle OutOfMemoryError
Wish to spend a day troubleshooting? Or make enemies among sysops? Registering pkill java to OutOfMemoryError events is one darn good way to achieve those goals. Read more