http://track.sipfoundry.org/browse/XX-9236 The backup needs to be decent sized to really expose the issue.
On 6/1/2011 7:08 AM, Matthew Kitchin (usenet/public) wrote: > I have a jira on this. I can look it up in a little while. This was the same > on 4.2.1 for me. I have one large system (4.2.1 still) with about 160 lines > and it eventually uses all 16 GB of RAM. > -----Original Message----- > From: Tony Graziano<[email protected]> > Sender: [email protected] > Date: Wed, 1 Jun 2011 08:01:25 > To: Sipx-users list<[email protected]> > Reply-To: Discussion list for users of sipXecs software > <[email protected]> > Subject: [sipx-users] stable repo (4.4.0) memory questions > > I have a recent 4.4.0 upgrade that at boot consumes just under 2GB of > ram at bootup. I rebooted the system at 5pm, and with very few actual > call flows, consumes the rest of the memory overnight (8GB). The only > thing happening at night is a backup. It has just over 100 lines > registered. It's on its own vlan, etc. > > I have seen the system on its first day of use then eat into swap and > start exhibiting "stuck" (like no prack) calls. > > I've disabled it for now in lieu of another method which should yield > more results tomorrow on whether or not it can be backed up without > consuming 5gb more of ram. > > Is there a limit to the memory the sipx backup can consume? > _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
