Yes, I'm still new to ASP.Net 1.1 & 2.0, but I've been using WinForms for a few years (since 2003 I think?), so maybe my perception on bottlenecks is skewed here.
We're running an enterprise level ASP.Net 1.1 application which also has many pages still in Classic ASP. The Server is "2003 Server" on a modern cutting edge server... core duo or core quad or whatever.
The database is SQL Server 2000.
This app has been around for a while, so this hasn't always been the OS or server computer.
In comming to this project, the developers keep on saying that we need to handle things clientside when possible. Not for ease of use, but to save the server from bottlenecking.
We have like 400 users max, spread throughout the day (if everyone had to use the app in a single day, which isn't always the case). How would you figure out how many concurrent users? Maybe a few hitting at relatively the same time.
I don't know, it just seems that we're stressing ways to prevent serverside processing and from my perspective, it doesn't even seem like we're comming close to maxing out the Web Server or SQLServer's capabilities, yet we're doing silly optimizations to avoid the overhead of a datatable.
Maybe I'm just spoiled being a winforms developer. Any thoughts?
We're running an enterprise level ASP.Net 1.1 application which also has many pages still in Classic ASP. The Server is "2003 Server" on a modern cutting edge server... core duo or core quad or whatever.
The database is SQL Server 2000.
This app has been around for a while, so this hasn't always been the OS or server computer.
In comming to this project, the developers keep on saying that we need to handle things clientside when possible. Not for ease of use, but to save the server from bottlenecking.
We have like 400 users max, spread throughout the day (if everyone had to use the app in a single day, which isn't always the case). How would you figure out how many concurrent users? Maybe a few hitting at relatively the same time.
I don't know, it just seems that we're stressing ways to prevent serverside processing and from my perspective, it doesn't even seem like we're comming close to maxing out the Web Server or SQLServer's capabilities, yet we're doing silly optimizations to avoid the overhead of a datatable.
Maybe I'm just spoiled being a winforms developer. Any thoughts?