development:benchmark
Dies ist eine alte Version des Dokuments!
Inhaltsverzeichnis
Middleware Benchmarks
description | RAM (MB) | CPU type | disk type | power consumption w/o disk (W) | power consumption incl. disk (W) | virtual or physical system | web server software | db software | os | commit | result (s) |
---|---|---|---|---|---|---|---|---|---|---|---|
OPTIPLEX 790 SF w/ APC | 4096 | Corei3-2100 @3.1 GHz | SATA? | ? | ? | virtual | apache2+php | mysql | Linux | 02c1ea557b927b5c7f90 | 0.13 |
volkszaehler.org w/ APC | 1024 | AMD 64 @1 GHz | SCSI | ? | ? | physical | apache2+apc | mysql | Linux | baa7ab92bf87e0479c97 | 0.6 |
volkszaehler.org w/ APC | 1024 | AMD 64 @1 GHz | SCSI | ? | ? | physical | apache2+apc | mysql | Linux | fe69f572bff79a13a62a | 0.61 |
volkszaehler.org w/o APC | 1024 | AMD 64 @1 GHz | SCSI | ? | ? | physical | apache2+apc | mysql | Linux | e4b1f69548f3e09ff837 | 0.811 |
volkszaehler.org w/o APC | 1024 | AMD 64 @1 GHz | SCSI | ? | ? | physical | apache2+apc | mysql | Linux | 2340233b5bb05da7d589 | 0.9 |
Seagate dockstar w/ usb stick | 128 | Marvel @1.2 GHz | USB2/flash | ? | 3.4 | physical | apache2+apc | mysql | Debian Squeeze | 2340233b5bb05da7d589 | 2.6 |
Seagate dockstar w/ 3.5„ HD | 128 | Marvel @1.2 GHz | USB2/3,5“ HD | 3.1 | ? | physical | apache2 | mysql | Debian Squeeze | fe69f572bff79a13a62a | 1.7 |
Seagate dockstar w/ 3.5„ HD | 128 | Marvel @1.2 GHz | USB2/3,5“ HD | 3.1 | ? | physical | apache2+apc | mysql | Debian Squeeze | 2340233b5bb05da7d589 | 2.6 |
IOmega iConnect w/ 2.5„ HD | 256 | Marvel @1 GHz | USB2/3,5“ HD | ? | 5 | physical | apache2+apc | mysql | Debian Squeeze | 0f6004bbec9c4fec027a | 2.12 |
Seagate dockstar w/ 3.5„ HD w/o APC | 128 | Marvel @1.2 GHz | USB2/3,5“ HD | 3.1 | ? | physical | apache2 | mysql | Debian Squeeze | 2340233b5bb05da7d589 | 3.2 |
Neoware ThinClient EON 4300s | 512 | Via Ezra @800 MHz | USB1.1/disk | 19 | ? | physical | apache2 | mysql | Ubuntu Lucid | 2340233b5bb05da7d589 | 1.43 |
Neoware ThinClient EON 4300s w/ APC | 512 | Via Ezra @800 MHz | USB1.1/disk | 19 | ? | physical | apache2+apc | mysql | Ubuntu Lucid | 2340233b5bb05da7d589 | 1.4 |
Foxconn NT525 w/ APC | 1024 | Intel Atom 525 DualCore @1.8Ghz | MicroSD Cheap&Slow | ? | 13 | physical | apache2+apc | mysql | Debian Squeeze | 2340233b5bb05da7d589 | 0.71 |
Foxconn NT525 w/o APC | 1024 | Intel Atom 525 DualCore @1.8Ghz | MicroSD Cheap&Slow | ? | 13 | physical | apache2 | mysql | Debian Squeeze | 2340233b5bb05da7d589 | 0.87 |
VMware w/o APC | 128 | Intel Core 2 Duo @2.4Ghz (only 1 Core in VM) | 2.5„ SATA | ? | ? | virtual | apache2 | mysql | Debian Squeeze | 8b65fa8ba25f149d7724 | 0.25 |
VMware w/ APC | 128 | Intel Core 2 Duo @2.4Ghz (only 1 Core in VM) | 2.5“ SATA | ? | ? | virtual | apache2+apc | mysql | Debian Squeeze | 8b65fa8ba25f149d7724 | 0.18 |
Synology NAS DS-109+ | 512 | Freescale PowerPC MPC8533 @1,06Ghz | 3.5„ SATA | 12 | 21 | physical | apache2 | mysql | Linux | 1.17 | |
Thinkpad Edge XAMPP Win7 w/ APC | 2048 | AMD II Neo K325 DualCore @1.3GHz | 2.5“ SATA | ? | 12 | physical | apache2+apc | mysql | Windows7 x64 | 0.84 | |
Thinkpad Edge XAMPP Win7 w/o APC | 2048 | AMD II Neo K325 DualCore @1.3GHz | 2.5„ SATA | ? | 12 | physical | apache2 | mysql | Windows7 x64 | 0.98 | |
PC-Engines Alix3d2 | 256 | AMD-Geode LX800-500MHz | CF4GB +8GB-USB-Stick | <5 | <5 | physical | apache2+apc | mysql | Debian Squeeze | 2.7 | |
HP Proliant L36N | 1024 | AMD II Neo Dual-Core @1.3GHz | 3.5“ SATA Raid1 | 25 | 30 | physical | apache2+php | mysql | FreeBSD 9 | 0.32 | |
RaspberryPi | 256 | ARM11 @700 MHz | 2 GB SD-Card (Medion) | n/a | 2.5 | physical | apache2+php | mysql | Debian Squeeze | 3.46 |
And how are the results being retrieved?
- import the demo dataset found in our git repo
- run this query:
http://<server>/<path to middleware>/data/a301d8d0-903b-1234-94bb-d943d061b6a8.json?from=1287541654974&to=1288488900567&tuples=1000&debug=5 e.g.: http://demo.volkszaehler.org/middleware.php/data/a301d8d0-903b-1234-94bb-d943d061b6a8.json?from=1287541654974&to=1288488900567&tuples=1000&debug=5
- find the reading somewhere a few lines above the bottom that looks something like this:
debug: { time: <benchmarkresult>
This is the time that passed while processing the request.
Remarks:
- try to make sure there is as little extra load as possible on the system while the request is performed
- give the request several runs; all (or most) requests should give more or less identical results; in case the results differ, submit an average
Not happy with your results?
Give performance a look!
development/benchmark.1342126699.txt.gz · Zuletzt geändert: 2012/07/12 22:58 von justinotherguy