Re: Initial 6.1 questions


On Tue, 13 Jun 2006, Danial Thom wrote:

Maybe someone can explain this output. The top line shows 99.6%idle. Is it just showing CPU 0s stats on the top line?

Two types of measurements are taken: sampled ticks regarding whether the system as a while is in {user, nice, system, intr, idle}, and then sampling for individual processes. Right now, the system measurements are kept in a simple array of tick counters called cp_time. John Baldwin and others have changes that make these tick counters per-CPU. The lines at the top of top(1)'s output are derived from those tick counters. Ticks are measured on each CPU, so those are a summary across all CPUs. To add cpustat support, we need to merge John's patch to make cp_time per-CPU (ie., different counters for different CPUs) and teach the userland tools to retrieve them. When you run top you'll notice that it adjusts the measurements each refresh. In effect, what it's doing is sampling the change in tick counts over the window, pulling down the new values and calculating the percentages of ticks in each "bucket" in the last window.

Robert N M Watson
Computer Laboratory
Universty of Cambridge
_______________________________________________
freebsd-performance@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-performance
To unsubscribe, send any mail to "freebsd-performance-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Initial 6.1 questions
    ... the system measurements are kept in a simple array of tick counters called cp_time. ... That doesn't explain why the Top line shows 99.6% idle, but the cpu idle threads are showing significant usage. ...
    (freebsd-performance)
  • Re: Initial 6.1 questions
    ... Two types of measurements are taken: ... simple array of tick counters called cp_time. ... each CPU, so those are a summary across all ...
    (freebsd-performance)
  • Re: Initial 6.1 questions
    ... system measurements are kept in a simple array of tick counters called cp_time. ... Ticks are measured on each CPU, so those are a summary across all ...
    (freebsd-performance)
  • Re: Initial 6.1 questions
    ... Two types of measurements are taken: ... changes that make these tick counters per-CPU. ... each CPU, so those are a summary across all ...
    (freebsd-performance)
  • Some initial postmark numbers from a dual-PIII+ATA, 4.x and 6.x
    ... I pulled down the postmark benchmark, and gave it a spin on a dual PIII ... the "alone" measurements, associated with the setup and tear-down of the ... While I didn't attempt to measure precise CPU usage as yet, ...
    (freebsd-performance)