Hi there,
seems you're issuing one request per insert.
Can you adjust the code on the client to consolidate the inserted data and
insert multible rows at a time like
insert into TABLE (`field1`,`field2`,`field3
VALUES
('data-1-1','data-1-2','da
('data-2-1','data-2-2','da
...
('data-n-1','data-n-2','da
The maximum rows you can insert is only limited by the max query size.
--TheDoctor
Main Topics
Browse All Topics





by: gurvinder372Posted on 2009-11-03 at 23:54:34ID: 25737229
Please mention/clarify,
1) If this is a web-application, Java-Client applet application or otherwise.
2) If you are using any connection pooling or any other mechanism to re-use the existing connection.
I suggest,
1) Create a connection (or a pool of connection) at the startup of the application, cache it and use these connection objects as and when required. A connection object should be thread-safe. Once a commit is done, connection should go back to the connection pool.
2) Insert and Delete code should be thread-safe (synchronized if possible), to avoid concurrency issues.
Let me know if this helped