
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-19-2010 03:45 AM
If I start the LS service again, CPU usage goes back up to 100% within 30 seconds of starting. It dips for a bit then sits at 100%. I'm assuming these 100% usages are happening when AD Scanning is going on.
I'm using Windows 2008 x64 (non-R2) with SQL Express 2005, one 2.3 GHZ single core CPU (server is a VM on vSphere), and 4 GB Memory. There are also 21 domains in our network and about ~3k workstations.
LS 3.5.2 would sometimes also tax the server at 100% but not constantly. LS 3.5.2 was running on the same hardware as above.
I'm now going to move the installation to a new VM running 2k3 R2 x86 with four 2.3 GHZ cores to see if that helps.
- Labels:
-
Archive

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-02-2010 05:03 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-22-2010 08:51 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-22-2010 08:50 PM
How many computers are in the database?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-22-2010 05:47 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-22-2010 06:18 PM
DGoodwin wrote:
Yes. If I open any page that I haven't opened before, sqlservr.exe goes to 100% for 3-9 seconds depending on the page.
There is an option somewhere is SQL that defines how many processors to use for each query.
You can try lowering this.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-22-2010 05:37 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-22-2010 05:33 PM
I did clear out the 98,000+ entries on the table dbo.tblntlogevent to see if it helped and no luck. I am going to have one of our sql guys look over as well.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-19-2010 06:53 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-19-2010 03:04 PM
