-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>> the above trace only shows a factor of 2 total penalty, but I've
>> seen up to a factor of 4 in other cases. There is no way that a
>> client-side driver should be taking several times longer than the
>> backend to process a SQL command :-(
> What version of DBD::Pg did you test with?
This is a problem with the newer versions as well. Maybe even worse,
as we had to do some contortions when the PQprepare 7.4/8.0 mess
appeared. However, we can definitely speed up that part of the code.
I'll see about doing this soon.
I still maintain the original test is brain-dead, however. :) It was
testing for "insert speed" by basically doing this:
for (1..1000) { $dbh->do("INSERT INTO testtable(a,b) VALUES (1,2)");
}
It's as if the people who wrote it *cough*mysql*cough* never heard
of prepare/execute and did not read the DBI docs.
It's very similar to the script on this page:
http://www.innodb.com/bench.php
- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200506121438
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iD8DBQFCrILHvJuQZxSWSsgRAkqnAKCoU1XAfE9nsQf11U0hM2P7Vt/uOACfSXmN
Dt9h3ACXGLEAXiIdjcXMLRg=
=8fiG
-----END PGP SIGNATURE-----
