Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker!apple!olivea!olivey!jerry From: jerry@olivey.olivetti.com (Jerry Aguirre) Newsgroups: news.software.b Subject: Re: expire oink Summary: incore dbz uses lots of memory Keywords: expire dbz memory swap Message-ID: <49312@olivea.atc.olivetti.com> Date: 29 Aug 90 19:56:10 GMT References: <1990Aug19.202420.140@m2xenix.psg.com> <1990Aug21.154310.20719@zoo.toronto.edu> <1990Aug22.165739.6918@lethe.uucp> Sender: news@olivea.atc.olivetti.com Organization: Olivetti ATC; Cupertino, CA Lines: 23 In article <1990Aug22.165739.6918@lethe.uucp> drew@lethe.uucp (Drew Sullivan) writes: >In article <1990Aug21.154310.20719@zoo.toronto.edu> henry@zoo.toronto.edu (Henry Spencer) writes: >>In article <1990Aug19.202420.140@m2xenix.psg.com> news@m2xenix.psg.com (Randy Bush) writes: >>>the hog, 11MB and four hours (while, for comparison, a full pathalias build >>That's awfully slow for a dbz expire. Ours typically takes 30 minutes to >My 386 runing Xenix take about 10 minutes to do a 22 day expire. I had it down to 8 minutes for 28 days of news and 60 days of history. All these comparisons are ignoring one vital factor, the amount of memory in the system. Expire runs very fast with the dbz INCORE option but it uses many megs of memory. The original poster claimed it was using 11 meg; He later stated that this was on a system with only 4 meg of physical memory. I was running with 16 Meg and expire was using most of that. I would assume that dbz has a fairly random access to the incore memory. That is going to be swap nightmare. Given that dbz has several ways to configure the incore option it can be difficult to tell. The original poster didn't think he was using incore but that 11 meg. size makes me think he is. (I know that in Bnews I have often wished for a little program that would compile and when run would print out what options it, and therefor news, was compiled with. Wading thru that mess of ifdef, undef, else define can be a real pain sometimes.)