Hi!
On 29-Nov-99 Bruce Momjian wrote:
>> On Mon, 29 Nov 1999 [EMAIL PROTECTED] wrote:
>>
>> > Yes! But I recommend backend pool too. What is it? The postmaster task
>> > runs now backend for each query. Good. But After query backend
>> > finished. I recommend to stay backend running within a some timeout.
>> > If the next query occured the postmaster redirect query to any idle
>> > backend or run a new one unless. Then backend serve some connections
>> > it shut down itself, this prevents memory leaks.
>> >
>> > Using this method we can get same speed like as with threads.
>>
>> Actually, with how fast Bruce has been able to get the start time on a
>> backend process, I seriously doubt that you'll get much more of a speed
>> up, but if you wish to work on creating a 'backend pool' of processes, I
>> don't think anyone will complain...
>
> 7.0 will be even faster on startup because of index use on cache loads.
Hmmm... I'll go to postgresql.org to read about...
> I couldn't measure a speedup because most other startup routines too
> more time, but I am sure some people will see speedup.
The startup speed depends on system load. When physical memory is exhausted or
CPU too busy the running of new process is not so fast...
Hmm... I should test I guess the time of running of new process using fork/exec
and using backend pool to compare...
SKiller
--------------------------
Sergei Keler
WebMaster of "ComSet"
E-Mail: [EMAIL PROTECTED]
http://www.comset.net
--------------------------
************
