:: 24-Nov-1999 15:30 (Wednesday) ::
Here’s some more info on what we’re seeing on statbox.
The problem that we’re running into is that as soon as we enable any
httpds, Sybase’s CPU load goes through the roof. With 5 httpds running,
we’re seeing CPU usage of 90% on a dual PII-300. Access to the database
is slow as hell, either from the web or locally.
The interesting thing is that this suddenly started after importing the
04 or 05 rc5 log yesterday. After doing some cleanup, the CSC run last
night was fine until the 07 CSC log, when things ground to a crawl. We
were seeing BCPs of ~50rows/sec, where they’re normally 1000s of
rows/sec.
So, the only theory I can think of is that the database has grown to a
size where we’re suddenly overflowing some cache or memory structure.
Unfortunately, sp_sysmon is of little value because it won’t run except
under the lightest of loads. With anything close to a normal load, it
just sits there, never returning from the call. When we do run it, we’re
seeing rather odd results, such as:
Task Context Switches Due To:
Voluntary Yields 10.0 1809.0 1809 47.3 %
Cache Search Misses 1.0 176.0 176 4.6 %
System Disk Writes 0.0 0.0 0 0.0 %
I/O Pacing 0.0 0.0 0 0.0 %
Logical Lock Contention 0.0 0.0 0 0.0 %
Address Lock Contention 0.0 0.0 0 0.0 %
Log Semaphore Contention 0.0 0.0 0 0.0 %
Group Commit Sleeps 0.0 0.0 0 0.0 %
Last Log Page Writes 0.0 0.0 0 0.0 %
Modify Conflicts 118.4 21323.0 21323 557.9 %
I/O Device Contention 0.0 0.0 0 0.0 %
Network Packet Received 1.5 265.0 265 6.9 %
Network Packet Sent 2.4 439.0 439 11.5 %
SYSINDEXES Lookup 0.0 6.0 6 0.2 %
Other Causes -112.1 -20196.0 -20196 -528 %