RE: Finding CPU hogs

Look at onstat -u and note the user processes that are running. Particularly note the users with large numbers of read and write activity. If you want more, then onstat -g ses {sess-id} to find the sql they are running. If a repeat says the same sql , then you likely have an application / database problem. Murray Wood -----Original Message----- From: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org]On Behalf Of Jeff Larsen Sent: Wednesday, February 09, 2000 7:19 AM To: informix-list@iiug.org Subject: Finding CPU hogs Is there any way to determine which user session might be causing oninit to hog the CPU? Can any of the onstat -g commands help?