Re: Portable stored procedures

From: sshaughnessy (steven_shaughnessy_at_yahoo.com)
Date: 02/10/04

  • Next message: Erwin Moller: "Re: is it difficut to deploy j2ee aplications at customer sites?" 
    Date: 9 Feb 2004 22:33:53 -0800

    The JDataStore file system is a single file store. In addition to the
    storage of tables, it allows random access file streams to be
    organized in a directory. Of course you can also store these as blobs
    in a table as well. The idea was to provide a portable,
    transactional, encryptable file system of database tables and
    arbitrary file streams. The support for file streams was added
    because it was easy, not because a lot of customers asked for it.

    The performance of stored procedures is probably more dependent on the
    runtime, then the stored procedure language itself. However, the
    execution of byte code compiled by hot spot is probably faster than
    any sql based stored procedure language. There was a huge investment
    in making hotspot and the jvm memory management which is not likely to
    be matched by a proprietary stored procedure language. A managed code
    language like java (no error prone pointers, memory management and
    exception handling) provides a trustworthy, powerful, object oriented
    language for writing stored procedures. Debugging and profiling java
    stored procedures can also be performed with high quality general
    purpose tools as well.

    As for the performance of java vs native databases, my experience is
    that it still boils down to the quality of your algorithms. For the
    most part I've been able to make raw java code as fast as C++. Most
    of the exceptions come from inefficient practices in sun's runtime
    java class libraries.
    There are an infinite number of ways to benchmark a database, so I
    won't say JDataStore is faster than any particular database across the
    board, but we have numerous real world cpu/memory intensive benchmarks
    where JDataStore decisively out performs popular established high
    performance native databases. That said it is easy to make slow java
    code and as I mentioned before, sun has accomplished this many times
    in their java runtime classes.

  • Next message: Erwin Moller: "Re: is it difficut to deploy j2ee aplications at customer sites?"