On 11/16/2005 15:51, 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.
> 
> 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.. ;)
> 

It's in there, and it's being exported, and we added HPO last year. We are
running LISTSERV 1.8e on Solaris 2.8 on a Sun Fire V480 with two 900 Mhz
processors and 4 GB of memory. There does not seem to be any correlation
between system load and LISTSERV performance.

----- extract from go.user -----
#
SMTP_FORWARD="localhost"
SMTP_FORWARD_1="5*localhost"
SMTP_FORWARD_2="5*localhost"

# -- Enable list exits &  use of exit input/output files
LIST_EXITS="EXIT-NOCHANGE EXIT-NOSIGNOFF"
EXIT_INPUT=1

# -- Treat username portion of email address as case-insensitive
IGNORE_EMAIL_CASE=1

# -- Accelerate web and catalog scan operations (HPO only)
TUNE_MANY_LISTS=1

export WWW_ARCHIVE_CGI WWW_ARCHIVE_DIR FILTER_ALSO FILTER_ALLOW SMTP_FORWARD
	SMTP_FORWARD_1 SMTP_FORWARD_2 LIST_EXITS EXIT_INPUT IGNORE_EMAIL_CASE
	TUNE_MANY_LISTS
----- end extract -----

--
Paul Russell
Senior Systems Administrator
OIT Messaging Services Team
University of Notre Dame