From: | sdv mailer <sdvmailer(at)yahoo(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: PostgreSQL pre-fork speedup |
Date: | 2004-05-06 04:56:34 |
Message-ID: | 20040506045634.95434.qmail@web60203.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I'll pretend I didn't see that last comment on
Windows. I wouldn't want to disappoint the users who
are eagerly expecting the Win32 port to complete
including myself. ;-)
Having said that, I think it's more the reason to get
a working pre-fork for Win32. Don't you think so?
--- "scott.marlowe" <scott(dot)marlowe(at)ihs(dot)com> wrote:
> On Wed, 5 May 2004, sdv mailer wrote:
>
> > Forking is quite fast on Linux but creating a new
> > process is still 10x more expensive than creating
> a
> > thread and is even worse on Win32 platform. CPU
> load
> > goes up because the OS needs to
> allocate/deallocate
> > memory making it difficult to get a steady state
> > resource consumption.
>
> Just a nit to pick here. In Linux, the difference
> between forking and
> spawning a new thread is almost nothing. Definitely
> less than a factor of
> 2, and most assuredly less than the quoted factor of
> 10 here.
>
> The fact that windows has a heavy process /
> lightweight thread design
> means little to me, since I'll likely never deploy a
> production postgresql
> server on it that needs to handle any serious load.
>
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs
http://hotjobs.sweepstakes.yahoo.com/careermakeover
From | Date | Subject | |
---|---|---|---|
Next Message | sdv mailer | 2004-05-06 05:22:39 | Re: PostgreSQL pre-fork speedup |
Previous Message | sdv mailer | 2004-05-06 04:39:43 | Re: PostgreSQL pre-fork speedup |