Subject | RE: [Firebird-Java] Re: Problems with type2 driver |
---|---|
Author | Ryan Baldwin |
Post date | 2004-01-21T15:09:17Z |
Hi All
always connect via the remote protocol. This is because until the threading
issues we were discussing before have been resolved firebirds current IPC
protocol will not work correctly when more then one thread/connection is
used.
approximatly
Embedded - Always fastest as long as not using RC4 or less(strange
performance problem with this/these). This is quite predictable.
IPC Type2 - Considerably faster then Type4 although due too threading issues
in the real world the granularity of locking that has too be done may not be
desirable. Also this mode is inaccesable with current jaybird.(plus only
usable where client and server are on the same machine)
TCP(remote) Type2 - Was always very slightly slower then Type4 mode.
Type4 - The baseline
Thanks
Ryan
-----Original Message-----
From: Roman Rokytskyy [mailto:rrokytskyy@...]
Sent: 21 January 2004 14:16
To: Firebird-Java@yahoogroups.com
Subject: [Firebird-Java] Re: Problems with type2 driver
Hi,
application directory structure and include current dir (".") in the
path. It should work.
heavy for small data transfers, embedded engine driver accesses file
directly from Java, there's no socket overhead at all.
Type 2 driver, with the IPC URL (server and port is not present)
should give your similar performance, but it will allow shared access
to the database (embedded engine locks the database for exclusive
use). Try to download jaybird.dll from SourceForge.net, maybe I sent
you an old version of it.
Best regards,
Roman Rokytskyy
Yahoo! Groups Links
To visit your group on the web, go to:
http://groups.yahoo.com/group/Firebird-Java/
To unsubscribe from this group, send an email to:
Firebird-Java-unsubscribe@yahoogroups.com
Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
>Type 2 driver, with the IPC URL (server and port is not present)Currently jaybird in type2 mode will not allow this too be done - it will
>should give your similar performance, but it will allow shared access
>to the database (embedded engine locks the database for exclusive
>use). Try to download jaybird.dll from SourceForge.net, maybe I sent
>you an old version of it.
always connect via the remote protocol. This is because until the threading
issues we were discussing before have been resolved firebirds current IPC
protocol will not work correctly when more then one thread/connection is
used.
> Besides i'm really impressed by the perfomance of the type 2 driverI did a fair bit of benchmarking a while back and my results where
> , it's nearly 100% faster for selects than type 4, even faster than
> interclient.
approximatly
Embedded - Always fastest as long as not using RC4 or less(strange
performance problem with this/these). This is quite predictable.
IPC Type2 - Considerably faster then Type4 although due too threading issues
in the real world the granularity of locking that has too be done may not be
desirable. Also this mode is inaccesable with current jaybird.(plus only
usable where client and server are on the same machine)
TCP(remote) Type2 - Was always very slightly slower then Type4 mode.
Type4 - The baseline
Thanks
Ryan
-----Original Message-----
From: Roman Rokytskyy [mailto:rrokytskyy@...]
Sent: 21 January 2004 14:16
To: Firebird-Java@yahoogroups.com
Subject: [Firebird-Java] Re: Problems with type2 driver
Hi,
> i got type 2 with embedded-server working now.I think you have to merge embedded server directory structure and your
> i need to put javaw.exe in the root directory of the
> embedded-server, this is working for testing purposes, but not for
> installations at our custumers.
application directory structure and include current dir (".") in the
path. It should work.
> Besides i'm really impressed by the perfomance of the type 2 driverThat's expected thing. Firebird's remote protocol seems to be too
> , it's nearly 100% faster for selects than type 4, even faster than
> interclient.
heavy for small data transfers, embedded engine driver accesses file
directly from Java, there's no socket overhead at all.
Type 2 driver, with the IPC URL (server and port is not present)
should give your similar performance, but it will allow shared access
to the database (embedded engine locks the database for exclusive
use). Try to download jaybird.dll from SourceForge.net, maybe I sent
you an old version of it.
Best regards,
Roman Rokytskyy
Yahoo! Groups Links
To visit your group on the web, go to:
http://groups.yahoo.com/group/Firebird-Java/
To unsubscribe from this group, send an email to:
Firebird-Java-unsubscribe@yahoogroups.com
Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/