C
Christian Kaiser
We needed to change a mainboard of a Win2000 server (defective condensers),
and after reinstalling Win2000 Server (same chipset, yet different disk
controller, so "inaccessible boot device, ..., the whole bunch)), the server
is very slow.
Scanning through the internet about good ideas, I found the "context blocks
queued/sec" an interesting counter, as it increases to very high values (for
only ONE client - me - it averages about 500,000 with a maximum of 1111,910
(!!!) with only little load). This server needs about 300 ms to answer some
inquiries (value taken from FILEMON). CodeWright or DevStudio are nearly
unusable if more than one file is opened.
What can I do to find out the reason? Where can I look?
It's an
CPU: Athlon Xp 3000+
RAM: 512 MB RAM
NIC: Intel Pro 100 S
Good ideas are welcome. Please.
Christian
and after reinstalling Win2000 Server (same chipset, yet different disk
controller, so "inaccessible boot device, ..., the whole bunch)), the server
is very slow.
Scanning through the internet about good ideas, I found the "context blocks
queued/sec" an interesting counter, as it increases to very high values (for
only ONE client - me - it averages about 500,000 with a maximum of 1111,910
(!!!) with only little load). This server needs about 300 ms to answer some
inquiries (value taken from FILEMON). CodeWright or DevStudio are nearly
unusable if more than one file is opened.
What can I do to find out the reason? Where can I look?
It's an
CPU: Athlon Xp 3000+
RAM: 512 MB RAM
NIC: Intel Pro 100 S
Good ideas are welcome. Please.
Christian