3 ms·
Very interesting reading. Some of my colleagues work with Vagrant or just-plain-old VMs for development and I have heard quite a bit of grousing about performa
by bhauer 13y ago
Very interesting reading. Some of my colleagues work with Vagrant or just-plain-old VMs for development and I have heard quite a bit of grousing about performance. It's nice to have some actual data.
For whatever reason, the matter that I found most fascinating is the application start-up time.
I chiefly work with Java web applications deployed on Resin. Some ten-odd years ago, when I first selected Resin as a web container, I did so because of its relatively quick start-up time. It's around 3 seconds to boot a modest application on modern hardware. Since then, I had lost sight of the importance of application start-up time. Resin and many competing but similar platforms (e.g., Play) support dynamic reloading during development, so a full container restart is fairly uncommon.
But your article makes me wonder if it would be of interest for us to include container and application start-up time in our framework benchmarks project. I think that's something we could fairly easily measure.
Thanks again for putting this together!
- bdon 13y agoI've found application boot time to be a pain point if you're running your tests frequently - I run mine several times a minute. For Ruby/Rails developers it's been especially bad, especially in JRuby. Some major patches have been made to Ruby(MRI) recently to help make this less of a problem: http://www.rubyinside.com/ruby-1-9-3-faster-loading-times-require-4927.html http://www.rubyinside.com/ruby-1-9-3-faster-loading-times-re... http://blog.tddium.com/2012/11/20/profiling-ruby/ http://blog.tddium.com/2012/11/20/profiling-ruby/