Re: DBI Performance Issues
- From: "Chris H." <chris@xxxxxxxxxxxxxxxx>
- Date: Mon, 28 Aug 2006 10:37:31 -0400
On Fri, 25 Aug 2006 17:56:42 +0000, xhoster wrote:
How fast is your network connection? I see barely any change in
performance at all between local and remote.
the real machine will be 100mbit to 100mbit via lan. the testing machines
that i used are from my home cable connection (8mb down/2mb up) to 100mbit
colo. its easy to blame the cable connection, however the traffic going
across the line during the updates are a whopping 7kbit/s which a 14.4k
could handle. thats why im at a loss for ideas. its like its refusing to
use the cpu or the network hardware during remote tests. as i dont have
iptraf on the actual machine that will run this, i cant say for certain
how much bandwidth its using on the lan...but i'd imaging not much if any
more than my home to colo tests.
I would suggest it is at a lower lever, at the network or at the compiled
binaries that DBD::mysql links against. Have you implemented the same
thing in another language (C, Java, Python) and seen better performance?
If not, I doubt your problem has anything to do with Perl or perl modules
per se.
Xho
i have not implemented this in another language, however, there are a few
changes. first the live script is run from a sun solaris machine using
dbi's sybase odbc driver to connect to a mssql database on a windows 2003
server machine. the dev script i've modified to suit my environment which
consists of mysql. the tables i have set up identical, and the data file
was scp'ed from the live machine and run against both databases to check
for performance differences.
the only difference short of this i can find is that on my colo box
running mysql local, and running the script local with 'localhost' as the
server to connect to will use 50% cpu for the perl script, and 50% cpu for
the mysql process.
running it from my home machine to the mysql box using 'domain.tld' as the
server to connect to, it uses less than .5% cpu as if its not even working
or attempting to work.
this effect is seen in the live version of the script too, with the remote
server in the connect string, the script on the solaris box will use less
than 1% cpu and the mssql server machine under task manager reports a cpu
usage of 8%-14% (it doesnt run this database exclusively).
i realize there are quite a few variables at play here, but im hoping its
something really simple im missing thats blocking it from just running at
its true speed.
i cant say how the dbi or dbd drivers on the solaris machine are compiled,
as i didnt set them up. the dbi and dbd drivers on both my home machine
and the colo box are standard gentoo compiled versions. as far as the
ebuild's are concerned, they are setting no additional options from the
defaults.
thanks.
--
Chris H.
http://www.nasland.nu
.
- Follow-Ups:
- Re: DBI Performance Issues
- From: xhoster
- Re: DBI Performance Issues
- References:
- DBI Performance Issues
- From: Chris H.
- Re: DBI Performance Issues
- From: xhoster
- DBI Performance Issues
- Prev by Date: integrate()
- Next by Date: Re: Out of memory! When running perl script on windows
- Previous by thread: Re: DBI Performance Issues
- Next by thread: Re: DBI Performance Issues
- Index(es):
Relevant Pages
|
