quote:Originally posted by Don YonceAn update ....1) A Network Trend chart was added to a Home Page or Summary View.The Network Trend charts were added in V7 and are VERY machine intensive since they need to scan the entire SQL table in order to generate a chart. We suggest that you do not place these on your Home Page, but instead have a link to a different view that contains them.You can also increase the Chart Cache timeout so that these charts will be generated less frequently.2) The Orion Server is monitoring Sun or Novel CPU and memory resources and the Polling Engine is encountering SNMP errors which causing much higher than normal CPU load on the server. This was a problem in an early pre-release, but was resolved in the final V7.0 release (released after 12/1/2003).3) The LSASS security process is running away. The LSASS process should normally run at 0% CPU load. But.. on some dual processor machines we have seen it run as high as 60%. This problem was first identified in November 2002 and reported to Microsoft. Microsoft has aknowledged that it is an issue, has worked hard in a solution, but has not been able to come up an acceptable solution that does not break structure problems in COM+ and thousands of legacy programs that depend on COM+.It is very easy to identify this issue. Is the LSASS process on your server running 20% to 60%? If so, then the NetPerfMon Service, SQL Server, and Web Site will be CPU starved. To correct the problem, simply shutdown the NetPerfMon Service, wait for it to stop completely and then restart. If you are more interested in the gory details of LSASS and COM+, send a note to development@solarwinds.netWe still have a couple of other leads into this issue that we are continuing to investigate.Thanks,Don
quote:Originally posted by keistYou should contact tech support they supplied me with a multiprocessor build that increased performance of the web site drasticaly.Dan