dotnet performance: We just upgraded from a 16-bit windows version of our mission-critical DB
app to a new version built on .NET 1.1. We replaced all servers and
workstations with powerful new hardware and upgraded our network to a
gigabit infrastructure. Now, instead of the client software connecting
directly to the SQL 2000 server, we have an in-house IIS server that sits in
between the clients and the new SQL 2000 server. The clients talk with IIS,
and IIS deals with the SQL server. Unfortunately, system performance is FAR
slower on the .NET system than we were used to on the old system, even
running on older hardware. I have only 15-20 clients using the system at
any one time, but even with only one user logged in performance is no faster
so it's not a server load issue. With the horsepower of my servers and
clients I think I should be getting much faster response. Some pages take 5
seconds or more to load, when the same data in our old system could be
displayed in a fraction of a second.

I'm looking for tips, tricks, suggestions, theories, incantations, black
magic... any suggestion or information that might help me to tweak more
performance out of this system. Our users' workloads have effectively
doubled since it now takes twice as long to do the same work. I should have
called this a "migration" instead of an "upgrade" because it certainly
doesn't feel like a step up from our previous system.

Thanks in advance,

Bryan

It all runs on a single subnet, so no routers involved. I think the
connection between servers is ok; I've copied large amounts of data across
it manually and performance is what you'd expect for a gigabit network.

It's a complete rewrite of the system; long overdue, since it was originally
written as a 16-bit windows application. It's had many version changes and
updates since then but it ran fine on XP Pro SP2 and was quite mature. The
..NET version is a complete redesign and rewrite from the ground up. It's
actually been around for 2-3 years now, so we're on v1.7. V 2.0 is due out
late next quarter.

Could on-access virus scanning on workstation, SQL server, or IIS server be
causing this?

Bryan


[quoted text, click to view]

Bryan,

It is just plain impossible to give you any specific remediation advice
based on the supplied info. It could be a whole bunch of things. Your
first step would be to profile the application and find out where the
bottlenecks are. Then if you still need remediation advice, you could
get some.

Incidentally, for the DB tuning side of things you might want to install
SQL Server 2005 someplace and use its admin tools against the SQL Server
2000 DB. The SQL Server profiling and tuning wizards are really
terrific and they do work against SQL2K DBs.

I hope you do find that the ultimate solution is simple.

Best,

--Bob

[quoted text, click to view]