in reply to Re: DB Connection pool
in thread DB Connection pool

Unless your database server has multiple processors it is unlikely that running multiple queries in parallel will be substantially faster than running the same queries serially.

Not necessarily true. Compiling a large project (say, a linux kernel) on a single CPU machine completes substantially faster with two processes (make -j2 ...) than it does in a single process, as this allows the CPU to keep compiling in one process while the other waits for disk access.

While I haven't tested whether this is also true of databases, I suspect that it is likely to be.

Replies are listed 'Best First'.
Re: Re: Re: DB Connection pool
by samtregar (Abbot) on May 07, 2002 at 18:12 UTC
    My experience with databases is that they are far less I/O bound than many other tasks. As long as your machine has sufficient free RAM and your database is properly tuned, your queries should not be waiting for disk access often enough to matter.

    Of course, it's worth testing. It might be that the proper setting for N is actually 2 * number of available CPUs.

    -sam

[reply]

In Section Seekers of Perl Wisdom