Re: Lyris

[James Cook <jcook @ netcom . com>]

On Thu, 28 Nov 1996, Eric Thomas wrote:

> Actually, this  is a  completely meaningless number  because it  does not
> exercise the  areas of  SMTP delivery  which are  difficult to  scale and
> implement in  an efficient  way, and  which are  your bottlenecks  as the
> workload increases. The  only thing it exercises is  the protocol engine,
> ie the code that  sends a HELO command, waits for  the answer, sends MAIL
> FROM:,  and so  forth.  This is  straightforward code  that  tends to  be
> implemented with  a similar level  of efficiency on most  products. There
> are only so many ways to format a RCPT TO: line and then send it over the
> socket. I wouldn't be surprised to  hear that you can get these 300k/hour
> using sendmail on  the same hardware, if you configured  and tuned it for


This thread on Lyris architecture and performance is educational in my 
view. I appreciate the detailed look.

It would also be helpful to suggest *meaningful* methods of testing or 
evaluating *real world* performance of listservers. For example, Lyris 
has a 30 day money back guarantee. So it is possible to have a no risk 
test period (except for time invested testing). To take greatest 
advantage of that period, what is the smartest method of testing it...or 
others?

Thank you.

James cook