On Wed, 16 Nov 2005, Valdis Kletnieks wrote: > On Wed, 16 Nov 2005 15:26:46 EST, Paul Russell said: > > > I will add this to our go.user file, however, with 32,000+ lists, LISTSERV > > initialization takes approximately 75 minutes, so I will need to schedule > > an outage to restart the service. > > Hmm.. I smell a rat, and a pointer to the *real* issue(s) here. Another for ref., we restart nightly: approx. 3,700 lists. 15 Nov 2005 23:59:04 LISTSERV(R) for unix version 14.4 starting... ... 15 Nov 2005 23:59:16 Initialization complete Sun Fire 280R w/ 2 900Mhz UltraSPARC-III+ and a generous 4G of memory. Also setting 'TUNE_MANY_LISTS=1' w/ an HPO license. 75 minutes is excessive: - 3,700 lists = 11 sec - 5,700 lists = 38 sec - 32,000 lists = 4,500 sec Is it possible that the number of files in "home" is pushing the server over the edge? Is it possible to hash the "home" directory? - Bill > We're running with about 5700 lists under 14.4, and our last restart: > > Nov 4 06:56:37 listserv.vt.edu lsv[3315]: LISTSERV(R) for unix version 14.4 starting... > ... > Nov 4 06:57:15 listserv.vt.edu lsv[3315]: Initialization complete > > Not huge iron either - Dell 2850 with 2 3.6GHz Xeons and 2G of memory. > > Maybe you need 'TUNE_MANY_LISTS=1' in go.user and/or an HPO license? 75 minutes > is just nuts (although it's what I'd have expected on our old Listserv box for > 32K lists - it had 200MHz 604e CPUs.. ;) >