Discussion Locked

How to interpret perfomance monitor

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am hoping someone can help me.

I have a NT server (BDC) which is supporting a number of applications incluign our Intranet, Clearquest (accessed via intranet and uses an SQL 7 Db ), A sybase datbase system for our timesheets, Exchange 5.5 and storage for our PVCS source code control system.

The box is running very slow - I am blaming clearquest as it was ok until this was added a ew months ago.

When looking at taskmanager I see two copies of sqlsvr.exe running - anyone know why?Also a program called STORE.EXE is taking up huge amount of memory - any one know whatthis is??

I've been running performance moniter on process, committed bytes and page faults - seems to be a lot of time when committed bytes are 100%, although% in use is running at about 50% We also get lots of page fault activity - sometime goes up to 4000 or 5000 per sec??

Does any one have any ideas on what this mught be, or where can I get useful info on what to monite and how to interpret the results?

5 replies

by mckaytech

Very likely, the short answer is that you're short on RAM. Very short...although I don't know how much you have so I can't make a recommendation on where to go from here. However, with what you have running, a full gig of RAM wouldn't be too much.

The first answer is correct in regards to STORE.EXE - it will take up as much memory as is available unless you tell it otherwise. You can do so by running the Exchange Optimizer and setting a limit on the amount of memory used by Exchange.

It is also possible that you could restrict the amount of RAM available to SQL Server and maybe even things out a little. It sounds like it was the installation of the SQL database that pushed things over the edge and that would not be an unusual event as it, like Exchange, is very RAM intensive.

Probably the best reference I can give you to sort out these parameters is an article on Microsoft's TechNet (#Q146005).

regards!

paul

This discussion is closed to new replies.