The Internet Archive discovers and captures web pages through many different web crawls.
At any given time several distinct crawls are running, some for months, and some every day or longer.
View the web archive through the Wayback Machine.
CPU burn-in test, stress test, stability test, temperature test, .
Simulate an older, slower machine, for software development purposes
Simulate heavy load on OS, to test system administration
procedures. See Suggested Usage - System Administrator on the Memory Load Test page for
Slow down speed of other applications to more easily
observe their operation e.g. to read error messages that are displayed
Examine the behaviour of dual-core and other multi-core
systems (check CPU utilization). At 100% Duty Cycle setting - is one
core loaded to 100% the other unloaded, or both loaded to 100%, or both
loaded to 50%?
Use Fossil PC Speed
to check PC speed reduction caused by this utility.
Note Fossil PC Speed before and after running CPU Load Test.
For accurate results, run Fossil PC Speed in a separate
process. Use ps or task manager, to display running processes, to
confirm. To make sure of this, use a different web browser software
(e.g. Firefox for PC Speed, Opera for CPU Load).
Firefox will run all browser instances in the same process.
As does Opera.
IE6 will run each instance in a separate process, but only
if not launched from an existing IE6 instance via File | New | Window.
CPU Load Test cannot seize more CPU resources than allocated
by the OS to the web browser. To increase the CPU load:
Increase the execution priority of the web browser process.
Run more than one instance of CPU Load Test, in separate
web browser processes.
Can be used to simulate application behaviour on older,
Run Fossil PC Speed on unloaded, target old machine to get
reading of its performance.
On unloaded test/development machine (presumably newer and
faster than target old machine), adjust CPU Load Test duty cycle, and
number of web browser instances, until roughly the same Fossil PC Speed
is obtained. Then run the application that is being developed, and test
for acceptable response time, race conditions.
If target old machine is not available, estimate a halving
of Fossil PC Speed for every two years older than test/development
machine. For example - test/development machine is new and Fossil PC
Speed is 800. To simulate a four year old machine, configure CPU Load
Test until the Fossil PC Speed is 200 (800 / 2 / 2).
Use at your own risk
These online tools are meant to be used by IT
professionals and power users. People who
know what they are doing and who understand the
limitations of web-based software
recognize the possibility of bugs in software, the
complexity of the interactions between applications, CPUs (including
multi-core), RAM, operating system (task scheduler, memory manager
etc). And therefore carefully interpret and check the results reported
by any software.
Send compliments, suggestions, complaints to:
(c) 2007 by Yuen Kit Mun, all rights reserved.
To support the development of this and other free
software ("Free as in beer"), please don't copy the code or place the
HTML file on an Internet web server (intranet or localhost web server
is okay, don't remove this copyright notice). But do tell others about