I am using the pre-compiled, downloadable castor-0.9.3 version. I've made some tests with JDO on small object updates / queries / deletes testing single transaction speed.  Comparing the results with the same amount of data transfer directly using JDBC (therefore eliminating the object<->table mapping overhead and simply executing insert / delete / select SQL commands), I've measured about 30 times more performance.
 
Unfortunately I cannot avoid using one update / delete / query per transaction, which I know is slow.
 
I'd like to know if there is something I could do about reducing this overhead of JDO, e.g. by compilation parameters, preference settings or other ?
 
Thanks,
 
Norbert

Reply via email to