[Mailman-Developers] 200 000 subscribers

[Ron Ohmer]

Well, that means that 40 percent of the time is spent dealing with it on the
client end.

Then the next step, is what portion of this overhead (16 seconds) is the web
server using?

What I am driving at is: What is the amount of time that Mailman is actually
using to deliver this page.  That is the amount of time you can hope to gain
with Mailman 3.


-----Original Message-----
From: Robby Griffin [mailto:rmg at terc.edu] 
Sent: Tuesday, March 16, 2004 11:39 AM
To: Heiko Rommel
Cc: 'Fil'; 'Mailman Developers'; Ron Ohmer
Subject: Re: [Mailman-Developers] 200 000 subscribers

On Tuesday, Mar 16, 2004, at 10:34 US/Eastern, Heiko Rommel wrote:

> On Tue, 16 Mar 2004, Ron Ohmer wrote:
>
>> I believe a large percentage of that time will be spent by your 
>> browser.
>>
>> You have a table, then ~3950 formatted lines (<LI> tag).
>>
>
> Especially if using older versions of Netscape Navigator the rendering 
> of large
> tables takes ages.  However, other browsers may be cheating by 
> displaying the
> search results even before it is complete (MSIE for example). To test 
> if it is
> really MM who is the bottleneck try the command line tools 
> (list_members etc).

Loading the page with lynx, it takes about 16 seconds before I'm 
prompted to accept a cookie, meaning the CGI has spent that amount of 
time producing no output. Afterwards, the page transfers in 4-5 seconds 
at 140kb/s. Rendering is ridiculously fast in lynx, of course.

	--Robby