Hi,
The performance of the data transfers using the direct socket connection
goes from <15 milli sec (in the lab) to ~32 milli sec (in pseudo
production env). But the database calls go from <1 sec to several
seconds (have not measured this yet). The database was exactly the same
in both trials. We are moving small amounts of data (<100 bytes) in any
query.
bogus ethernet cards or network equipements ?
last year one ethernet cards on our firewall start to produce errors,
resulting in a really slow transfert rate and long latency, could this
apply to you ?
Does this shed any light?
Celona, Paul - AES wrote:
I am running mysql 4.0.18 on Windows 2003 server which also hosts my
apache tomcat server. My applet makes a connection to the mysql
database
on the server as well as a socket connection to a service on the same
server. In the lab with only a hub between the client and server, the
application performs well and data is transferred quickly. In the
deployed environment with a pair of gateways in between, socket
performance is not affected much, but the application gui bogs down on
the database queries. Performance is so slow that some simple GUI
updates take up to 5-7 seconds with only a simple 1 table update
occurring.
Does anyone have experience with this and/or can provide some insight?
From: gerald_clark
If your applet is making connections on each page, you might be having
reverse dns problems.
From: Shawn Green
It sounds like you don't have all of your indexes declared on your
production database.
There could also be an issue of network lag between your application
server and your database server. The best performing applications use
the fewest trips to the database to accomplish what they need. You may
want to examine your application design and minimize the number of trips
you make to the server.
For example, assume you run two queries, one to get a list of
departments and another to list the people in each department. If you
design your application to perform one lookup to get the departments
list then loop through that list to find the department's people, you
are making way too many "trips" to the database. A more efficient design
is to JOIN the two tables and submit just one query. Then, as you
process the results, you detect when the Department value changes and
adjust your OUTPUT accordingly.
Could it be the volume of data you are trying to present is just that
much larger with your production data set than it was with your
development dataset that it's taking that much longer to format the
output?
You provided so FEW details of the actual issue, it's VERY hard to be
more helpful. Can you provide more details of what isn't working the way
you want and why?
Shawn Green
Database Administrator
Unimin Corporation - Spruce Pine
************************************
This e-mail and any files transmitted with it are proprietary and intended
solely for the use of the individual or entity to whom they are addressed. If
you have received this e-mail in error please notify the sender. Please note
that any views or opinions presented in this e-mail are solely those of the
author and do not necessarily represent those of ITT Industries, Inc. The
recipient should check this e-mail and any attachments for the presence of
viruses. ITT Industries accepts no liability for any damage caused by any virus
transmitted by this e-mail.
************************************
--
Philippe Poelvoorde
COS Trading Ltd.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
