|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Christine Wolak (cwolak
SCT.COM)Date: Wed Oct 03 2001 - 09:35:43 CDT
We too have been having performance problems with our application on
Windows 2000. Here's a summary of where we are now, in case it helps
anyone:
Our application was taking about 2.3 times as long under Win2k as compared
to NT. We got a hotfix from Microsoft which got us about 0.6 of that 2.5
back. This hotfix was supposed to provide MTS emulation mode (as far as
max apts per thread, or max threads, or something like that), but the
emulation mode itself didn't make any difference in our application - just
having the hotfix did.
Then, all of a sudden we got all but 0.1 of it back. A significant
improvement! The traces we did pointed to the function
GetQueuedCompletionStatus, which seemed to have to do with I/O in some
way. I think I think this improvement came because of
manually/specifically stopping and restarting DTC (rebooting the machine
did NOT do the trick). Microsoft never did say for sure why or whether
stopping DTC fixed this, what might have caused it to take up so much time
all of a sudden, how to keep it from happening, etc. We haven't seen the
problem crop up again, but if we do, Microsoft says that they'll want to do
some poking around at call stacks and stuff.
Another thing that did not apply to us but may apply to others was a memory
allocation issue that was broken in SP1 but fixed in SP2.
We also did some testing to force everything into ONE BIG CONTEXT, and that
had no real impact on our performance. We have one big
package/application, though, so maybe that has something to do with it.
I must respectfully disagree with Richard Blewett, who said "for a properly
configured server, Win2k is simply faster than NT". This is NOT the case
for every COM application, and as far as I could tell from Microsoft,
there's not much in the way of "configuration" of your server that you can
do to speed up performance, anyway. Maybe for WELL-DESIGNED systems, or
small systems (we have 71 DLLs in COM+), or some other scenario.
But "configuration of the server" didn't seem to have anything to do with
it.
----------------------------------------------------------------
Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
contains important info. Save time, search the archives at
http://discuss.microsoft.com/archives/index.html .
To unsubscribe, mailto:DCOM-signoff-request
DISCUSS.MICROSOFT.COM
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]