Re: Overwhelming a Web Application Server

The harder question is how to enforce it. It seems that the
application server would need to know precisely the number of active

sessions.

"Active" is a funny word, someone that hasn't been to the site in 6
hours, but you have an 10 hour session timeout, are they "active"?

However, while this is a fun discussion, I think we're doing exactly
what I warned about at the start of the thread, we're "fixing" the
problem w/out actually measuring where the problem is. Yes, I know this
is all from a user-point of view anyway, since you don't have access to
the server in this case, but even if you did... we've latched onto
session as an issue, and in fact the issue may be as simple as a poorly
indexed database. After all, all databases are fast when there's one
user and 100 rows.

-Walden