Hello.
Can you figure out in which state the queries from JBoss spend time the most? You may use your own program and 'SHOW PROCESSLIST' statement or something like: mysqladmin -i 1 -r processlist. I don't see a big difference between JBoss and a normal Java application except JBoss uses it's own connection pool. The problem could be at JBoss side. Another suggestion - what happens if you switch from the prepared statements to usual queries? BTW your innodb_log_file_size is about 12 times smaller then innodb_buffer_pool_size. According to: http://dev.mysql.com/doc/mysql/en/innodb-configuration.html it should be about 25% of the buffer pool size. >In our J2EE application which runs under JBoss 3.2.2 we are generating >own queries by using a connection from JBoss connection pool. This are prepared >statements >- needed from JBoss 450-500 millis >- nedded from normal Java application 15-25 millis Rafal Kedziorski <[EMAIL PROTECTED]> wrote: -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
