I don't sure for jdbc driver - it can be what you claim and oracle's java stuff isn't too good
however, locking is important - when you test application with small number of users and queries/dml then you will have good performance, but when you deploy application you will have worst performance
oracle have rollback version for every query - have doubled data - it mean that with one user it is slower, but later reader don't block another readers and writers and writer don't block another writers/reader (except if another writer write to same row)
this behavior mean superior performance in multiuser no matter what are data
it is > 10 and more times quicker in multiuser - blocking users have horribel impact on performance
postgresql have similar architecture, but postgresql lock foreign key constraints and if you test in multiuser without referencial integrity then it work fine, but if you have correct defined database with referencial integrity then performace is worst than oracle
on this list exists more thread about performance jdbc and hibernate - hibernate is slower (for simple query) because hibernate do much more than jdbc - populate bean, collection, cache etc
true test is in multiuser environment, only - if you use database with only one user then
Quote:
You answered that oracle is faster on average, especially when you have concurrent accesses.
I don't see that we disagree here.
if you use database in single user/single query then i agree, but it is rear cases
I forget - it isn't in only multiuser - this is true for single user when user do more queries/dml to same date
Quote:
Even then, some databases are faster than others. Even if oracle costs an arm and a leg it might be slower than competitors for stuff like this.
there is now free oracle database (oracle 10g express , 1 gb ram 4 gb data constraints)
4 gb in oracle data is big - oracle save space good and you will not easy break this constraint