Driver Performance
These tests use straightforward jdbc code using driver defaults.
There are no optimizations or adaptations for interclient.
String Tests
| ODBC
| IC
| jConnect
| DG Broker
| DG Bridge
| dbANYWHERE
| DriverX
|
Insert 10,000 Char(10)
| 21,562
| 13,437
| 64,516
| NP
| 262,469
| 45,985
| 21,922
|
Insert 1,000 Char(100)
| 2,312
| 1,484
| 9,703
| 201,375
| 31,172
| 6,765
| 8,687
|
Insert 100 Char(1,000)
| 281
| 219
| 5,500
| 20,312
| 2,781
| 2,250
| 250
|
Insert 10 Char(10,000)
| 94
| 93
| 2,859
| 2,219
| 719
| 2,610
| 1,937
|
Select 10,000 Char(10)
| 3,859
| 2,719
| 4,609
| ?
| 3,234
| 10,015
| 14,907
|
Select 1,000 Char(100)
| 422
| 329
| 2,016
| 985
| 953
| 1,265
| 1,313
|
Select 100 Char(1,000)
| 109
| 109
| 563
| 40,953
| 406
| 313
| 156
|
Select 10 Char(10,000)
| 94
| 62
| 437
| 4,625
| 78
| failed
| 110
|
Blob Tests
| ODBC
| IC
| jConnect
| DG Broker
| DG Bridge
| dbANYWHERE
| DriverX
|
Insert 10,000 10-byte Blobs
| 81,938
| 48,563
| NP
| NP
| NP
| 134,125
| 27,297
|
Insert 1,000 100-byte Blobs
| 6,140
| 2,672
| 405,781
| 201,375
| 32,625
| 14,110
| 1,906
|
Insert 100 1,000-byte Blobs
| 2,282
| 2,000
| 45,860
| 20,328
| 5,593
| 4,547
| 326
|
Insert 10 10,000-byte Blobs
| 2,250
| 875
| 3,922
| 2,312
| 1,391
| 2,859
| 281
|
Insert 1 100,000-byte Blobs
| 1,406
| 94
| Overflow
| 500
| 1,002
| 2,906
| 78
|
Select 10,000 10-byte Blobs
| 45,062
| 55,391
| ?
| NP
| ?
| 167,828
| 17,500
|
Select 1,000 100-byte Blobs
| 5,484
| 5,672
| 55,812
| 404,047
| 11,391
| 9,078
| 1,594
|
Select 100 1,000-byte Blobs
| 1,125
| 594
| 5,218
| 40,797
| 1,375
| 1,719
| 156
|
Select 10 10,000-byte Blobs
| 4,000
| 78
| 610
| 2,609
| 203
| 360
| 63
|
Select 1 100,000-byte Blobs
| NP
| 47
| ?
| 1,203
| 110
| 312
| 31
|
You wouldn't see this kind of variation
with ODBC drivers for a couple reasons:
they've been around longer and they're
not networked so you don't see client library
functionality embedded in the driver as
you do with JDBC.
This is using the latest 1.50 release, which is quite a lot
faster than the 1.12 release.
Of course, times will vary depending on hardware;
it's the relative performance that's important.
NP stands for "no patience", but could be construed as non-polynomial ;-)
Send comments or suggestions to interclient@interbase.com