> Has anyone else had a problem with top on SPARC? It > seems > to run OK for a while, then it stops responding to > keystrokes > (like "q"), and then it stops updating, at which time > it starts > using a *lot* of CPU. Trussing it hasn't helped. This > seems > to have been a problem with sxce (and Open Solaris) > forever...
Not an answer, but some random apocrypha: Try prstat, unless you really need something that top does and prstat doesn't. prstat should usually use less CPU than top from what I've read. (Some of the design choices in top favored portability and/or scalability over performance.) Don't leave top (or even prstat) up all the time, unless of course you're very sure you're the only person on the system doing that. There are too many stories of systems bogged down, where the top half dozen or so processes were (you guessed it) top itself. If you use top, consider using the -s seconds option, with some number like at least 15, and preferably 60 or so, unless that would result in your phone ringing more, some SLA being violated (or if you're a developer, in not noticing some performance issue that you're trying to spot). The default 5 second updates mean that top is doing a lot of work, and also are likely to mean that if it has leaks or other bugs, they'll show up that much sooner. If you just want to see system load and CPU usage rather than the specific offending processes, consider sdtperfmeter (on SXCE). I don't know if there's a GNOME client for rstatd, but if there is, that would hopefully be on OpenSolaris (instead). -- This message posted from opensolaris.org
