Re: Benchmarking SQL drivers

And yet some more simplifications:

>This is 3940 queries running in batches of 1:
>16.2s  pgsql    Pike 8.1 (new driver, multithreaded)
>16.5s  MySQL    Pike 8.1
>15.2s  pgsql    Pike 7.8 (old driver, single threaded)
>21.3s  postgres Pike 8.1 (C-libpq)

We now get (batches of 1):
15.5s  pgsql    Pike 8.1 (new driver, multithreaded)
16.5s  MySQL    Pike 8.1
15.2s  pgsql    Pike 7.8 (old driver, single threaded)

>This is 3940 queries running in batches of 2:
>20.3s  pgsql    Pike 8.1 (new driver, multithreaded)
>19.4s  MySQL    Pike 8.1
>20.3s  pgsql    Pike 7.8 (old driver, single threaded)
>34.8s  postgres Pike 8.1 (C-libpq)

We now get (batches of 2):
20.0s  pgsql    Pike 8.1 (new driver, multithreaded)
19.4s  MySQL    Pike 8.1
20.3s  pgsql    Pike 7.8 (old driver, single threaded)

The higher batchcount tests yielded no significant difference to the 
previous benchark.

Getting even higher performance means that I would have to abandon the
Pike-only driver solution, and I would have to start using a cmod
helper module again.
However, since the new driver is only 2% slower than the old driver,
it is not worth the trouble to try and weed that out.
-- 
Stephen.