In 2003 I met this guy who was doing Computation Fluid Dynamics and he had to use this software written by physics engineers in FORTRAN. 1 Gig of ram wasn't yet the standard for a desktop pc at that time but the software required at least 1 Gig just to get started. So I thought what is the problem after all you are supposed to be able to allocate upto 2G on a 32 bit system even if you don't quite have the memory and you have sufficiently big swat space. Still, the software didn't load on Windows. So, it seems that Windows does not overcommit.
--- On Fri, 29/8/08, Matthew Wakeling <matthew(at)flymine(dot)org> wrote:
> From: Matthew Wakeling <matthew(at)flymine(dot)org>
> Subject: Re: [PERFORM] select on 22 GB table causes "An I/O error occured while sending to the backend." exception
> To: pgsql-performance(at)postgresql(dot)org
> Date: Friday, 29 August, 2008, 4:56 PM
> On Fri, 29 Aug 2008, Craig James wrote:
> > Disable overcommitted memory. There is NO REASON to
> use it on any modern
> > server-class computer, and MANY REASONS WHY IT IS A
> BAD IDEA.
> As far as I can see, the main reason nowadays for
> overcommit is when a
> large process forks and then execs. Are there any other
> modern programs
> that allocate lots of RAM and never use it?
> Nog: Look! They've made me into an ensign!
> O'Brien: I didn't know things were going so badly.
> Nog: Frightening, isn't it?
> Sent via pgsql-performance mailing list
> To make changes to your subscription:
Send instant messages to your online friends http://uk.messenger.yahoo.com
In response to
pgsql-performance by date
|Next:||From: Gregory S. Youngblood||Date: 2008-08-29 16:37:56|
|Subject: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception|
|Previous:||From: Greg Smith||Date: 2008-08-29 16:15:17|
|Subject: Re: select on 22 GB table causes "An I/O error occured
while sending to the backend." exception|