ThinkPad:Benchmarking: Difference between revisions
From Wiki³
Line 25: | Line 25: | ||
=systemd-analyze (boot speed)= | =systemd-analyze (boot speed)= | ||
This plot is a detailed graphic of the boot sequence. | This plot is a detailed graphic of the boot sequence. | ||
{{Console|1=systemd-analyze plot ~/boot.svg}} | {{Console|1=systemd-analyze plot > ~/boot.svg}} | ||
[[File:ThinkPad X220 Boot Analysis.svg|570px]] | [[File:ThinkPad X220 Boot Analysis.svg|570px]] | ||
=memtest86= | =memtest86= | ||
Memtest86 was installed into the rEFInd boot loader by installing the {{mono|memtest86-efi}} package. | Memtest86 was installed into the rEFInd boot loader by installing the {{mono|memtest86-efi}} package. |
Revision as of 11:21, 20 July 2017
UNDER CONSTRUCTION: The document is currently being modified! |
Back to Category:ThinkPad
For basic testing I installed the following packages.
# yaourt -S mesa-demos hdparm |
dd (cpu)
Using dd in conjunction with any steam-processing CPU-intensive program to provide a simple CPU benchmark. It may not be very accurate though.
# dd if=/dev/zero bs=1G count=10 | md5sum |
10+0 records in 10+0 records out 10737418240 bytes (11 GB, 10 GiB) copied, 20.3283 s, 528 MB/s 2dd26c4d4799ebd29fa31e48d49e8e53 - |
CPU Temperature peaked around 64C during the test. |
I then performed a rough 5 minute test.
# dd if=/dev/zero bs=1G count=160 | md5sum |
160+0 records in 160+0 records out 171798691840 bytes (172 GB, 160 GiB) copied, 324.407 s, 530 MB/s 8f75e24931ccd52edfc887601023073b - |
CPU Temperature was a constant ~70C with peaks of 71-72C hitting as high as 74C near the end. |
dd (ssd write)
# dd if=/dev/zero of=$HOME/tempfile bs=1M count=1024 conv=fdatasync,notrunc status=progress |
1024+0 records in 1024+0 records out 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 9.93576 s, 108 MB/s |
glxgears (vsync)
# glxgears |
Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. 304 frames in 5.0 seconds = 60.715 FPS 301 frames in 5.0 seconds = 60.049 FPS 301 frames in 5.0 seconds = 60.050 FPS 301 frames in 5.0 seconds = 60.050 FPS 301 frames in 5.0 seconds = 60.048 FPS 301 frames in 5.0 seconds = 60.049 FPS 301 frames in 5.0 seconds = 60.050 FPS 301 frames in 5.0 seconds = 60.048 FPS 301 frames in 5.0 seconds = 60.050 FPS 301 frames in 5.0 seconds = 60.048 FPS 301 frames in 5.0 seconds = 60.045 FPS 301 frames in 5.0 seconds = 60.055 FPS 301 frames in 5.0 seconds = 60.049 FPS 301 frames in 5.0 seconds = 60.049 FPS |
hdparm (ssd read)
# sudo hdparm -Tt /dev/sda |
/dev/sda: Timing cached reads: 12822 MB in 2.00 seconds = 6414.67 MB/sec Timing buffered disk reads: 790 MB in 3.00 seconds = 263.13 MB/sec |
systemd-analyze (boot speed)
This plot is a detailed graphic of the boot sequence.
# systemd-analyze plot > ~/boot.svg |
memtest86
Memtest86 was installed into the rEFInd boot loader by installing the memtest86-efi package.
# yaourt -S memtest86-efi |
PassMark MemTest86 V7.3 Free Intel Core i7-2640M @ 2.80GHz clk/Temp : 2791 MHz / 85C L1 Cache : 64K 20.76 GB/s L2 Cache : 256K 16.76 GB/s L3 Cache : 4096K 13.49 GB/s Memory : 8085M 10.74 GB/s RAM Info : PC3-10600 DDR3 1332MHz / 9-9-9-24 / Samsung M471B5273CH0-CH9 AddrMode: 64-bit Pass: 4 / 4 Errors: 0 # Tests Passed: 17/17 (100%) Lowest Error Address: N/A Highest Error Address: N/A Bits in Error Mask: 0000000000000000 Bits in Error - Total: 0, Min: 0, Max: 0, Avg: 0 Max Contiguous Errors: 0 |
unixbench
BYTE UNIX Benchmarks (Version 5.1.3)
https://github.com/kdlucas/byte-unixbench
System: | noc: GNU/Linux |
OS: | GNU/Linux -- 4.11.9-1-ARCH -- #1 SMP PREEMPT Wed Jul 5 18:23:08 CEST 2017 |
Machine: | x86_64: unknown |
Language: | en_US.utf8 (charmap="UTF-8", collate="ANSI_X3.4-1968") |
CPUs: | Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz (5584.6/5586.7/5585.0/5585.1 bogomips) Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET, Intel Virtualization |
Uptime: | 11:07:16 up 0 min, 1 user, load average: 0.29, 0.08, 0.02; runlevel unknown |
Benchmark Run: 4 CPUs; 1 parallel process
|
Benchmark Run: 4 CPUs; 4 parallel processes
|