Re: [Assp-test] Use both MySQL ( DB:) and BerkeleyDB ( for other) = flat files == _terrible_ memory usage Re: Antwort: Re: Antwort: Re: Antwort: Memory footprint

Hi! Looks like I'll be creating another VM with Debian 32bit. I bumped the current VM up to 2GB and upgraded again. It's holding steady at 1.7GB. But under 12057, it was fine. Are You shue, what in this version rebuildspam worked Ok? IMHO, rebuildspam process, for example, may be

Re: [Assp-test] Use both MySQL ( DB:) and BerkeleyDB ( for other) = flat files == _terrible_ memory usage Re: Antwort: Re: Antwort: Re: Antwort: Memory footprint

Victor Miasnikov wrote: Are You shue, what in this version rebuildspam worked Ok? It would appear that it's caused by rebuildspam. I've since moved over to Debian 32bit (Squeeze) and saw the same issues. Disabling rebuildspam over night, checking this morning shows that I'm at 430MB is

[Assp-test] Use both MySQL ( DB:) and BerkeleyDB ( for other) = flat files == _terrible_ memory usage Re: Antwort: Re: Antwort: Re: Antwort: Memory footprint

Hi! Do you use any DB ? No, just flat files. And, I just checked again. it's now running at 1.9GB and 112MB swap flat files == _terrible_ memory usage This VVMWin 2003 x86 720Mb for OS + 1Gb for soft = 5 . . 7 workers ( MySQL ( or other SQL Server) + BerkeleyDB _absolutely_

Re: [Assp-test] Use both MySQL ( DB:) and BerkeleyDB ( for other) = flat files == _terrible_ memory usage Re: Antwort: Re: Antwort: Re: Antwort: Memory footprint

Victor Miasnikov wrote: flat files == _terrible_ memory usage But under 12057, it was fine. Running around 800MB. Doug -- Ben Franklin quote: Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety.