New-age Transactional Systems - Not Your Grandpa's OLTP
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Werner Schuster on May 12, 2009
One argument for using Ruby 1.9.1 is the significanlty increased performance. New benchmark results come from running realworld, existing applications and pit 1.8.x, JRuby and 1.9.1 against each other:
We ported Acunote - our online enterprise project management and Scrum software to both JRuby and Ruby 1.9 and ran our set of performance benchmarks.
Ruby 1.9.1 and JRuby both provide significant improvements over 1.8.6, with 1.9.1 in the lead over JRuby, although there is some discussion in the comments about ways to improve JRuby's performance with some command line flags.
Performance improvements in 1.9.1 don't just come from a faster VM, but also from some of the new features. Muhammed Ali shows how to scale a web application using Ruby 1.9.1's Fibers. On the other hand, Muhammed also points out an issue with Object#extend leaking memory in 1.9.1.
Meanwhile, 1.8.6 is still the only option for some projects, due to some missing libraries on 1.9.1. Because of that, there's a lot of interest in fixing some bottlenecks in 1.8.6. Joe Damato has been investigating some of the issues over at his blog. For instance, he investigates the story behind --enable-pthread and why disabling the setting brings 30% performance gains. In another article, Joe and Aman Gupta investigate a problem with the Ruby GC - and came up with a tiny patch that fixes some problems with the GC and EventMachine:
* Speeds up GC by 2-3x because of the huge decrease in stack frame size.
* Fixes an open bug in EventMachine where using threads with Epoll causes lots of slowness. The reason is that each thread will inherit an ~800,000 byte stack that gets copied in and out every context switch.
* This results in an increase from 500 requests/sec to 7000 requests/sec when using Sinatra+Thin+Epoll+Threads. That is pretty ill.
Finally, Viktor Hokstad has been writing a series on compiling Ruby for some time now. A recent entry talks about some of the problems making Ruby fast and possible optimizations.
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
Why NoSQL? A primer on Managing the Transition from RDBMS to NoSQL
Monitor your Production Java App - includes JMX! Low Overhead - Free download
Complimentary Gartner (Hype Cycle for Cloud Security) Report
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
No comments
Watch Thread Reply