Rod Dunne <[EMAIL PROTECTED]> wrote: > What is the real advantage of using NestedVM?
SQLite is really useful as a file format and I can think of a lot of cases in Java where you need to store something reasonably complex in a file but don't want the hassle of a native library and performance is not much of a worry. So mostly it's about convenience. Sun really doesn't care for the idea of native libraries and thus it has always been difficult to get JNI to work. I have answered a lot of emails from people who just can't work out java.library.path. > Is it faster? No. It is slower. How much, I am unsure. The test suite takes a lot longer to run, but that is mostly overhead from starting NestedVM 89 times. Inside a single connection, speed seems reasonable, but I will do more tests in the coming week. > Was this only possible because SQLite doesn't use any platform specific > API calls and so the runtime of NestedVM could handle all the external > calls? NestedVM implements a decent subset of POSIX under UnixRuntime.java. The only big thing that was missing was file locking, because it did not come along until Java 1.4. I implemented this, so now SQLite with os_unix.c runs easily. Though the fact that SQLite is designed to be portable does help a lot. > You still have a Mac and Windows distribution, how come? They are smaller and faster. If you can use them, you should. I only dropped Linux because I can't be bothered setting up a cross compiler for it. d --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SQLiteJDBC" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups-beta.google.com/group/sqlitejdbc?hl=en -~----------~----~----~----~------~----~------~--~---
