Specific to Java, the synchronization has been loosened up quite a bit
(with careful analysis, so no, it's not dangerous), to prevent deadlocks
when using pool managers such as C3P0. We also removed a static
synchronization bottleneck when using multibyte character sets, which
showed up under high load.
Ah.... yes.. awesome. Yeah... synchronized can be safe to use but a
real performance killer.
5.0 also contains the performance feature that will rewrite
[Prepared]Statement.executeBatch() into either multi-valued inserts or
batched statements to save round-trips, by adding
"rewriteBatchedStatements=true" to your JDBC URL configuration.
Interesting..... it didn't dawn on me to use PreparedStatements... The
old bulk prepared statements are/were amazingly slow :-/
Check this out:
http://flickr.com/photos/burtonator/203543409/
totally clean up my writes:
http://www.feedblog.org/2006/07/using_on_duplic.html
I'm now using ON DUPLICATE KEY UPDATE and this has resulted in a real
performance boost.
Onward!
4 messages in com.mysql.lists.javaRe: MySQL Connector/J 5.0.3 Has Been ...