|
Last change
on this file since 103698 was 99016, checked in by vboxsync, 2 years ago |
|
manual: Some scm corrections for dita files. bugref:10302
|
-
Property svn:eol-style
set to
native
-
Property svn:keywords
set to
Id Revision
|
|
File size:
1.1 KB
|
| Line | |
|---|
| 1 | <?xml version='1.0' encoding='UTF-8'?>
|
|---|
| 2 | <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
|
|---|
| 3 | <topic xml:lang="en-us" id="ts_host-freq-boost">
|
|---|
| 4 | <title>Performance Variation with Frequency Boosting</title>
|
|---|
| 5 |
|
|---|
| 6 | <body>
|
|---|
| 7 | <p>
|
|---|
| 8 | Many multicore processors support some form of frequency
|
|---|
| 9 | boosting, which means that if only one core is utilized, it can
|
|---|
| 10 | run possibly 50% faster or even more than the rated CPU
|
|---|
| 11 | frequency. This causes measured performance to vary somewhat as
|
|---|
| 12 | a function of the momentary overall system load. The exact
|
|---|
| 13 | behavior depends strongly on the specific processor model.
|
|---|
| 14 | </p>
|
|---|
| 15 | <p>
|
|---|
| 16 | As a consequence, benchmarking on systems which utilize
|
|---|
| 17 | frequency boosting may produce unstable and non-repeatable
|
|---|
| 18 | results. This is especially true if benchmark runs are short, of
|
|---|
| 19 | the order of seconds. To obtain stable results, benchmarks must
|
|---|
| 20 | be run over longer periods of time and with a constant system
|
|---|
| 21 | load apart from the VM being tested.
|
|---|
| 22 | </p>
|
|---|
| 23 | </body>
|
|---|
| 24 |
|
|---|
| 25 | </topic>
|
|---|
Note:
See
TracBrowser
for help on using the repository browser.
