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.
News
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
JRuby 1.0.1 release, JRuby 1.1 plan posted
Posted by Werner Schuster on Aug 23, 2007
A plan for JRuby 1.1 was also posted. The release is scheduled to happen before RubyConf in early November. The plan:
- compiler complete
- AOT compilation working with jrubyc
- stdlib all precompiled
- gem install precompilation
- virtual filesystem-inside-JVM (maybe) or hacked rubygems that can run out of an archive
- performance improvement to be quantified...java integration, execution, memory reduction·
- Yarv bytecode execution and compilation (maybe)
- AST sharing as an option (sharing across runtimes)...need to explore AOT compilation and its (positive?) effect on memory too
- real threading brutalization, testably multithread-safe core classes (maybe, needs heavy testing on many-core systems)
- Java API rubification, perhaps with require 'javax.swing' and so on·
Note: AOT compilation refers to Ahead Of Time compilation, meaning that Ruby source code can be compiled down to class files. This is in contrast with JIT compilation, which happens at runtime, Just In Time.
AST sharing is supposed to reduce memory usage when multiple JRuby runtimes share a single JVM process. An AST is an Abstract Syntax Tree, a data structure representing the source code, which is used by the interpreter and the various compilers (AOT, JIT).
RelatedVendorContent
Monitor your Production Java App - includes JMX! Low Overhead - Free download
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
18 agile and lean practices for effective software development governance
No comments
Watch Thread Reply