![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
|
If you provide more informations like the query and how many rows it returns, it should be easier help you. |
|
Field | Type | Null | Key | Default Extra | +-------------------------+------------------+------+-----+---------------------+----------------+ contentId | int(11) unsigned | | PRI | NULL auto_increment | name | text | | | | publishDateTime | datetime | | | 0000-00-00 00:00:00 | | expireDateTime | datetime | | | 0000-00-00 00:00:00 | | contentTypeDefinitionId | int(11) | YES | | NULL | parentContentId | int(11) | YES | | NULL | creator | text | | | | repositoryId | int(11) | | | 0 | isBranch | tinyint(4) | | | 0 | isProtected | tinyint(4) | | | 2 | +-------------------------+------------------+------+-----+---------------------+----------------+ |
#4
| |||
| |||
|
#5
| |||
| |||
|
|
The MySQL-client is 4.1.7, too? Yes |
#6
| |||
| |||
|
#7
| |||
| |||
|
|
The MySQL-client is 4.1.7, too? Yes The localhost mysql command is version 4.1.7-standard The remote query browser is version 1.1.1 gamma The remote JDBC driver is version 3.0.16-ga |
#8
| |||
| |||
|
|
Are you seeing the slowdown only from your java app? Or from all clients? |
|
In the changelog for the 3.0.16 connector, they disabled BufferedInput as they were having problems with it on some systems. You should be able to pass useUnbufferedInput=true in the jdbc url to get this back. I think they are working on their own implementation to get buffered input back in the new 3.1 connector. |
#9
| |||
| |||
|
|
Are you seeing the slowdown only from your java app? Or from all clients? I see this slowdown from my java app AND from the remote MySQL client application (called MySQL Query Browser 1.1.1 and 1.1.2). Basically I see the slowdown from all clients that are remote machines, but I do not see it when I execute the queries on localhost (the server on which the database is running) In the changelog for the 3.0.16 connector, they disabled BufferedInput as they were having problems with it on some systems. You should be able to pass useUnbufferedInput=true in the jdbc url to get this back. I think they are working on their own implementation to get buffered input back in the new 3.1 connector. I experienced the slowdown with the 3.0.15 driver so I upgraded to the 3.0.16 driver and have the same problem. Any insight? |
#10
| |||
| |||
|
|
Are you seeing the slowdown only from your java app? Or from all clients? I see this slowdown from my java app AND from the remote MySQL client application (called MySQL Query Browser 1.1.1 and 1.1.2). Basically I see the slowdown from all clients that are remote machines, but I do not see it when I execute the queries on localhost (the server on which the database is running) In the changelog for the 3.0.16 connector, they disabled BufferedInput as they were having problems with it on some systems. You should be able to pass useUnbufferedInput=true in the jdbc url to get this back. I think they are working on their own implementation to get buffered input back in the new 3.1 connector. I experienced the slowdown with the 3.0.15 driver so I upgraded to the 3.0.16 driver and have the same problem. Any insight? THanks again, Frank |
![]() |
| Thread Tools | |
| Display Modes | |
| |