Crud. Meant this to go to the list. ---------- Forwarded message ---------- From: Jonathan S. Shapiro Date: Saturday, March 24, 2012 Subject: Retrospective Thoughts on BitC To: Florian Weimer <[email protected]> Cc: "Jonathan S. Shapiro" <[email protected]>
On Friday, March 23, 2012, Florian Weimer <[email protected]> wrote: > * Jonathan S. Shapiro: > >> - Run-time optimization has very negative consequences for startup times >> - especially in the context of transaction processing. Lots of hard data on >> this from IBM (in DB/2) and others. It is one of the reasons that "Java in >> the database" never took hold. > > Are you sure about this? It seems to be more of a technical issue > because both the Oracle JVM and databases each bring their own > operating system substrate with them and are thus at odds. Nowadays, > startup times are comparable to VMs which can execute inside a > database server process. Here's the key fact, as measured circa 1990: Typical DB/2 transaction duration: 150,000 instructions Native instructions required to reach first bytecode of main in IBM's JVM: 1,500,000 instructions Note the JVM hasn't done anything actually useful by that point. This datum is what prompted all of the work to pickle the initialized state. It's definitely possible to embed a safe language in a database effectively. Because of the profligate nature of the libraries, Java isn't going to be that language and neither is C#. shap
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
