Re: jdbc performance in Solaris

"Joe Smith" <nospam_at_nospam.com> wrote:
> >
> > I suggest you try setting the following environment variables and
> > restart your Java application (the second one is needed if your
> > application is 64-bit; if not, setting it is harmless):
> > export LD_LIBRARY_PATH=/usr/lib/lwp
> > export LD_LIBRARY_PATH_64=/usr/lib/lwp/64
>
> >
> > Please let us know if you find anything. If you find Bobby's suggestion
> > (below) works, also let us know. Thanks.
> >
>
> Well, nothing new around here. Bobby's suggestions and yours haven't
> improved the performance.
> I'm not sure if the threading model of java is really an issue; the
> problem is in fact the performance of a single java.sql.Connection
> object, running in a single thread.
>
> When I launch several instances of the test program several times, or a
> multithreaded version, oracle is able to absorb the load; what I found
> strange is the "factor" difference between Windows and solaris. As a
> reminder, in Windows, the connection with autocommit on is around 1.5
> times slower (400 insertions/second without autocommit, 250-300 with
> autocommit), whereas in solaris, this factor may go up to 10 (440 / 44).

Have you tried adding an explicit commit inside the loop of the java code? Maybe the autocommit isn't doing what it is supposed to be doing in one of the test cases.

Otherwise, it sounds like Solaris instance has it's redo logs on much slower disk than the Windows instance; or maybe Windows has some kind of write-caching going on.

Xho

-- 
-------------------- http://NewsReader.Com/ --------------------
Usenet Newsgroup Service                        $9.95/Month 30GB