[Delayed response, sorry!]
Stefan Parvu wrote:Hi David,
>> The classic tools for doing capacity planning measure
> operation/transaction rate and time taken, rather
> > than resource usage.
>>
>> Once you've *done* the planning, then you correlate
>> that with the amount of resources you used a
If anyone's interested, a few improvements to ptime(1) went back into build 104.
The default resolution for ptime(1) is now nanoseconds, not milliseconds.
ptime(1) now gives you microstate accounting with the -m flag.
ptime(1) can give you a snapshot of stats for a running process with
the -p fl
> http://www.teamquest.com/resources/webinars/display/30/index.htm
> Without the www, it goes nowhere (;-))
Many thanks. Interesting.
stefan
___
perf-discuss mailing list
perf-discuss@opensolaris.org
Whoops, the TeamQuest webinar link should be
http://www.teamquest.com/resources/webinars/display/30/index.htm
Without the www, it goes nowhere (;-))
--dave
--
This message posted from opensolaris.org
___
perf-discuss mailing list
perf-discuss@opensola
> corestat isn't integrated into Solaris because it
> hasn't been productized and has some issues (eg. must be
> run as root, prevents anyone else from using the CPU
> performance counters while it is running, only works for
> Niagara processors, may not be sufficient for doing capacity
> planning
