Hi Wayne,
We probably run user counts of the same order of magnitude on Imail however over many smaller (though still beefy) servers, we are looking to get better use out of our servers and scale the number of users up, whilst using SQL to allow better administration.
Is there any particular part of the Imail software that falls over more often.
In particular I'd be really interested in problems you've experienced with the IMAP4 and SMTP services.
Also is this the standard ODBCuser.dll or a custom fixed version?
As an aside we experience some problems whilst hammering a competing, but similar, product when the amount of active threads or handles were pretty large (1000+, 2 processors), windows NT seemed to lose connection to shares and other RPC based systems. We basically put this down to the ratio of NT server threads to application/service threads, we didn't get much evidence though.
As an other aside I would wonder what happens when the dll is being called by many threads at once to provide connections to the SQL server. The documentation for the dll seems to suggest that it is kept active after the first connection, I wonder if it can handle multiple threads at all. (I do not really know enough about multithreading to comment on this last bit.)
Thanks for any experiences you had.
Steven Moore
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Wayne Maw
Sent: 15 December 1999 15:56
To: [EMAIL PROTECTED]
Subject: Re: [IMail Forum] Scalability
We run more than that, and wouldn't recommend it, especially running against
a SQL server.
It's unreliable (stops authenticating users for no reason caused by bad ODBC
.dll), and easily chokes (if max smtp sessions is set to 60+ to clear the
queue faster, dll errors start occurring all the time), Looking for a better
alternative at the moment.
(The server hardware is quad xeon,1Gbram + very large raid)
Wayne.
{Callnetuk.com Admin}
