07-08-2008 11:59 PM
Recently I install Cisco LMS 3.0 (Campus Manager 5.0, Cisco View 6.16, CiscoWorks Assistant 1.0, Common Services 3.1, Default Fault Manger 3.0, Internetwork Performance Monitor 4.0, Resourse Manger Essiential 4.1, LMS Portal 1.0) on Machince which is more advance as per Cisco Recommendation.
Machine Specification is (OS W2K3-R2 with SP2, Intel(R) Xeon(TM) 3.4GH (Quard Processor), HDD 200GB with 4 GB RAM and pagging File is also 4 GB.
Currently LMS discover 200 devices and its performance is very degrated when I see PF which is utlized around 75% (3.5 GB out of 4GB).
Thanks.
07-09-2008 12:53 AM
mostly this is because of a virus scanner running on the server. If this is the case, exlude the complete LMS installation directory (..\CSCOpx)from the files and directories being scanned.
You can also check the Taskmanager and look fock for GGScript.exe. If this process is highly consuming CPU and memory, just kill that process (but the problem might reappear)
There are some updates and patches for LMS available on CCO which you should install on your server or order the update from LMS 3.0 to LMS 3.1 (free if you have SAS contract).
07-09-2008 01:34 AM
Thanks Mermel;
But as per my observation, I think this issue is not related to Virus Scanner. Because out of 3.3 GB PF (Pagging File) 2 GB PF is used by tomcat application and around 1 GB is used by Java application.
Thanks,
07-09-2008 03:27 AM
07-09-2008 10:26 AM
Try the Performance Tuning Tool:
07-09-2008 10:28 AM
And by the way, you should look into your Discovery settings. The default configuration is not really 'efficient'.
07-17-2008 02:24 AM
do you still have the performance problems?
as per recommendation, the pagefile should be at least 1,5x RAM (better 2x) (even when you think the system has enough physical RAM!)
I your situation increasing the page file size will decrease the value of pagefile usage but that is mathematics and I do not beliefe it will increase performance...
perhaps with Process Explorer from Mark Russinovitch (http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx) you can find the reason for the performance degregation.
Some other good links for memory basics are:
http://support.microsoft.com/kb/555223/en-us/
http://en.wikipedia.org/wiki/Commit_charge
- in the last article there is a hint how to configure 'Process Explorer' to make use of Microsofts' debugging utilities and 'Symbols'. You can download the debugging utilities from:
http://www.microsoft.com/whdc/devtools/debugging/default.mspx
and use Microsofts online Symbol-Server when you enter this string as the 'Symbols path':
.sympath[+] srv*DownstreamStore*http://msdl.microsoft.com/download/symbols
(according to Microsoft, downloading the 'Symbols' instead of using the online server will be around 750MB of data)
But you do NOT need the debugging utils and 'Symbols' for to use 'Process Explorer'; it will just give you some enhancements..
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide