Hi, > Hi Kirill, > > Kirill Korotaev wrote: > > > - AFAIK, "load" is very rough estimation for scheduler, since processes > > can fall asleep and awake in such a moments that they won't be accounted > > in timer interrupt. We had examples of such loads even in real life. > > I mean how much "fair" is such a scheduler with timeslice-based class > > management? Do you have any data on this? > > Probably my explanation confused you. Our CPU controller calculate per > class CPU load by own, and it is not equivalent to the load average, > which is an average length of runqueue.
I feel "load" would be a wrong term, misleading us. It's a kind of total time each class has used, which is used to determine time-slices of every processes. The trick to calculate the value is that old runtime is less weighted. "volatile total time" would be a good term. > Anyway, the following is a sample results to show how much fair > in terms of CPU proportional ratio. I chose Himeno Benchmark, which is > a CPU intensive work load. It is easy to run benchmark to estimate CPU > MFLOPS. I also run several dhrystone benchmark in background > in order to let the dhrystone eat the all free CPU slots. Otherwise, > Himeno Benchmark uses all CPU resource without regard to the CPU > guarantee. Thank you, Hirokazu Takahashi. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech
