> -----Original Message-----
> From: LISTSERV site administrators' forum [mailto:LSTSRV-
> [log in to unmask]] On Behalf Of Eric Thomas
> Sent: Tuesday, February 26, 2008 12:30 AM
> To: [log in to unmask]
> Subject: Re: Web interface 'slow'
>
> > It turns out the problem was too many files in the listserv\main
> > directory. Not too many lists.
> >
> > We enabled content_filter a while back - moderating any message that
> > our spam tagging system designated as spam. Most of the list owners
> > were just ignoring the messages about approval so the .OK files were
> > just hanging around. 29000 of them.
>
> This is probably due to the infamous 8.3 filename emulation in Windows,
> which is necessary if you want to run 16-bit applications. Few people
> still use 16-bit code, but the feature is enabled by default and it can
> have a huge performance impact. Unfortunately, turning it off can
> sometimes break third-party applications even though they no longer run
> in 16-bit mode. It is a gamble on a multi-purpose server, but you can
> usually do it without problem if LISTSERV is the only thing you run on
> the machine.

Yep 8.3 is enabled. It wasn't on the previous server but it looks like I missed that setting when I built this one. Grrrr. It's a listserv only box but there is some FC HBA management software on it that we'll have to check out and see if its compliant.


> For permanent relief, you can disable this through a registry entry.
> See:
>
> http://support.microsoft.com/kb/121007
>
> NTFS can actually handle very large directories as long as you disable
> the 8.3 feature. It was the fastest file system for LISTSERV when
> introduced 14 years ago, nowadays this is no longer the case but it
> remains one of the top performers, but only if you disable this.
>
>   Eric

Thanks for the information.

        Al

--

Al Lilianstrom
CD/LSC/CSI/CSG
[log in to unmask]