Thanks for the reply, Walden. Based on your observations and follow-up questions, it sounds like dealing with this type of problem is not simple, actually. A stress test tool may sound simple, but does it really pinpoint bottlenecks? And what if the problem is not a bottleneck, but resource contention, instead?
"Don't try fixing the problem until you know what the problem is." "The problem is seldom where you think it is."
Those were great observations.
Some of this discussion is hypothetical for me because I'm not closely affiliated with the university - just a father of a couple students who suffered through the registration process.
But since I develop Web applications, I'd like to avoid getting snagged by that type of problem in any of my deployments.
Perhaps based on limited knowledge, it seems to me that Web servers and Application servers are not very well equipped to manage complex and intense workloads. Seems like a good subject to discuss.
Nathan.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
