Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
john.burns
Posting Yak Master
100 Posts |
Posted - 2006-09-27 : 14:01:00
|
I have a SQL server 2000 clusterd server w/ w2k3 OS. (8 processors with 24GB RAM)DB is 20gbI have average processor time of 62%.. this seems high for an average (users are impacted by slow performance at times).I have basically cleared all major areas of bottlenecks for any problems:I/O --> average disk queue length =.65CPU --> Processor queue length = .25 Memory --> (cachesize * 8,192 = amt. of RAM in use by SQL) 159,044 * 8,192= 1,302,888,448Network --> (bytes total sec/currentbandwidth... > .6 =high) 168/1000000000 = .000000168 I have about 120 concurrent conncections and nearly 400 batch requests/sec .Front end Application has a lot of search functionality and uses full-text search. Anyone have any problems with FTS??When entering search screen user is returned a resultset of 1000 records in a a READ_ONLY SCROLLcursor before even doing any custom searching. Search stored procedures are highest cpu consumers. It is my theory that as system gets busier that these search procedures that return paging resultsetsare having a cumulative degrading effect on processor time.Anyone have any thoughts or comments?Thanks |
|
|
|
|