OK then I'm lost. It's got to either be a bug in how amazon ec2 instances work or severely fragmented memory because you've got a TON of kernel cache available. On Wed, Sep 26, 2012 at 3:00 PM, Shiran Kleiderman <shirank1@xxxxxxxxx> wrote: > Hi > Yes, same machine. > > Thanks for your help. > > > On Wed, Sep 26, 2012 at 10:55 PM, Scott Marlowe <scott.marlowe@xxxxxxxxx> > wrote: >> >> On Wed, Sep 26, 2012 at 10:41 AM, Shiran Kleiderman <shirank1@xxxxxxxxx> >> wrote: >> > Hi >> > Thanks again. >> > Right now, this is free -m and ps aux and non of the crons can run - >> > can't >> > allocate memory. >> >> OK, so is the machine you're running free -m on the same as the one >> running postgresql and the same one you're running cron jobs on and >> the same one you're running apache on? >> >> Also please don't remove the cc for the list, others might have an >> insight I'd miss. >> >> > cif@domU-12-31-39-08-06-20:~$ free -m >> > total used free shared buffers >> > cached >> > Mem: 17079 12051 5028 0 270 >> > 9578 >> > -/+ buffers/cache: 2202 14877 >> > Swap: 511 0 511 >> > > > > > > -- > Best, > Shiran Kleiderman > +972 - 542380838 > Skype - shirank1 > -- To understand recursion, one must first understand recursion. -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
