Programmi Linux per BenchMark, Stress Test ed OverClock

[Jhack]

uh chi si rivede. eh ormai è da un bel pò che non aggiorno più :\

quando ho più tempo aggiungo e dò una sistemata al thread.

[giacomosmit]

Un pò di lavoro per jack :P
Parto con le info sul pc:
CPU:i7-6700
MOBO:gigabyte-ga-z270x-ultra-gaming
RAM:Corsair CMU16GX4M2C3000C15 Vengeance
GPU:asus dual gtx 1060 6 gb

Poi, il SO è arch con su i3-wm naturalmente 64 bit

Bench

Burning test CPU : https://s1.postimg.org/9tkkq8l1n3/burningtest_CPU.png

Burning Test GPU 2D : https://s1.postimg.org/1kiwucxi9r/burni ... GPU2_D.png

Burning Test GPU 3D: https://s1.postimg.org/7zbk1xx40v/burni ... GPU3_D.png

Burning Test RAM: https://s1.postimg.org/77bfydq8b3/burningtest_RAM.png

jetstream: https://s1.postimg.org/17g17tphrz/jetstream1.1.png

Octane 2.0 : https://s1.postimg.org/49oon7rrmn/octane2.0.png

Systester 2M 1 turno 1 threads : https://s1.postimg.org/3sbecswolr/syste ... treads.png

systester 2M 1 turno 2threads : https://s1.postimg.org/813d0t5frj/syste ... hreads.png

systester 2M 1 turno 4 threads : https://s1.postimg.org/7xwih9f0fj/syste ... hreads.png

Systester 2M 1 turno 1 threads : https://s1.postimg.org/254bm53n2n/syste ... hreads.png

Systester 2M 1 turno 2 threads : https://s1.postimg.org/19xcz0rrbz/syste ... hreads.png

Systester 2M 1 turno 4 threads gauss : https://s1.postimg.org/416f73nqbj/syste ... hreads.png

Hardinfo

Codice: Seleziona tutto

CPU Blowfish
------------

-CPU Blowfish-
<big><b>This Machine</b></big>	3400 MHz	1.148	
Intel(R) Celeron(R) M processor         1.50GHz	(null)	26.1876862	
PowerPC 740/750 (280.00MHz)	(null)	172.816713	

CPU CryptoHash
--------------

-CPU CryptoHash-
<big><b>This Machine</b></big>	3400 MHz	1097.154

CPU Fibonacci
-------------

-CPU Fibonacci-
<big><b>This Machine</b></big>	3400 MHz	1.223	
Intel(R) Celeron(R) M processor         1.50GHz	(null)	8.1375674	
PowerPC 740/750 (280.00MHz)	(null)	58.07682

CPU N-Queens
------------

-CPU N-Queens-
<big><b>This Machine</b></big>	3400 MHz	0.377

FPU FFT
-------

-FPU FFT-
<big><b>This Machine</b></big>	3400 MHz	0.604	

FPU Raytracing
--------------

-FPU Raytracing-
<big><b>This Machine</b></big>	3400 MHz	2.540	
Intel(R) Celeron(R) M processor         1.50GHz	(null)	40.8816714	
PowerPC 740/750 (280.00MHz)	(null)	161.312647	

Poi faccio anche gli altri quando ho tempo..

uh chi si rivede. eh ormai è da un bel pò che non aggiorno più :\

quando ho più tempo aggiungo e dò una sistemata al thread.

questo dovrei dirlo io o noi .

[ale multimediale]

Weee!!Ciao raga
Ah gia,ho anche i geekbench
https://browser.geekbench.com/geekbench3/8461071

[ANXANX]

Intel® Core™ 2 Duo Processor T7600 2.33 Ghz @ 2.33 Ghz sistema operativo a 64 bit
Benchmarks Hardinfo:

Blowfish 7,56 s
CryptoHash 182,016 MiB/s
Fibonacci 2,818 s
N-Queens 15,305 s
CPU Zlib 0,297 HiMarks
FFT 7,585 s
Raytracing 8,402 s
GPU Drawing 7990,557 HiMarks

[ANXANX]

Intel® Core™ 2 Duo Processor T7600 2.33 Ghz @ 2.33 Ghz sistema operativo a 64 bit
Benchmarks Hardinfo:

Blowfish 7,56 s
CryptoHash 182,016 MiB/s
Fibonacci 2,818 s
N-Queens 15,305 s
CPU Zlib 0,297 HiMarks
FFT 7,585 s
Raytracing 8,402 s
GPU Drawing 7990,557 HiMarks

Ho ripetuto il test dopo gli ultimi aggiornamenti del microcode itel:
Blowfish 7,61 s
CryptoHash 181,75 MiB/s
Fibonacci 2,80 s
N-Queens 14,91 s
CPU Zlib 0,28 HiMarks
FFT 7,52 s
Raytracing 8,39 s
GPU Drawing 5620,51 HiMarks

L'unico ad avere avuto impatto è il disegno della GPU, ma credo che sia per via degli altri aggiornamenti e quindi non legato al processore

Per chi ha processori moderni e colpito dalle vulnerabilità recenti ha subito un calo di prestazioni in questi test?

[ale multimediale]

Non noto differenze su geekbench dopo le patch http://browser.geekbench.com/geekbench3/8536679 Anzi in single ho fatto qualcosina in piu

EDIT: Anche hardinfo è simile al precedente senza patch
CPU Blowfish 1.081
CPU CryptoHash 1053.549
CPU Fibonacci 1.244
CPU N-Queens 0.385
FPU FFT- 0.618
FPU Raytracing 2.371

CPU:sempre i7-7600

[noel80]

E' del 2023, mi sembra molto pratico: https://github.com/JonMagon/KDiskMark

If you have any ideas, critics, suggestions or whatever you want to call it, please open an issue.

lol

[noel80]

Segnalo anche iostat, che' e' nel pacchetto sysstat, utile per capire anche i tempi d' attesa del disco (GNOME Disks integra questa funzionalita' KDE Partition manager no).

Codice: Seleziona tutto

Synopsis
iostat [ -c ] [ -d ] [ -N ] [ -n ] [ -h ] [ -k | -m ] [ -t ] [ -V ] [ -x ] [ -z ] [ device [...] | ALL ] [ -p [ device [,...] | ALL ] ] [ interval [ count ] ]
Description
The iostat command is used for monitoring system input/output device loading by observing the time the devices are active in relation to their average transfer rates. The iostat command generates reports that can be used to change system configuration to better balance the input/output load between physical disks.

The first report generated by the iostat command provides statistics concerning the time since the system was booted. Each subsequent report covers the time since the previous report. All statistics are reported each time the iostat command is run. The report consists of a CPU header row followed by a row of CPU statistics. On multiprocessor systems, CPU statistics are calculated system-wide as averages among all processors. A device header row is displayed followed by a line of statistics for each device that is configured. When option -n is used, an NFS header row is displayed followed by a line of statistics for each network filesystem that is mounted.

The interval parameter specifies the amount of time in seconds between each report. The first report contains statistics for the time since system startup (boot). Each subsequent report contains statistics collected during the interval since the previous report. The count parameter can be specified in conjunction with the interval parameter. If the count parameter is specified, the value of count determines the number of reports generated at interval seconds apart. If the interval parameter is specified without the count parameter, the iostat command generates reports continuously.
Reports
The iostat command generates three types of reports, the CPU Utilization report, the Device Utilization report and the Network Filesystem report.

CPU Utilization Report
    The first report generated by the iostat command is the CPU Utilization Report. For multiprocessor systems, the CPU values are global averages among all processors. The report has the following format:

    %user

            Show the percentage of CPU utilization that occurred while executing at the user level (application).

%nice

    Show the percentage of CPU utilization that occurred while executing at the user level with nice priority.

%system

    Show the percentage of CPU utilization that occurred while executing at the system level (kernel).

%iowait

    Show the percentage of time that the CPU or CPUs were idle during which the system had an outstanding disk I/O request.

%steal

    Show the percentage of time spent in involuntary wait by the virtual CPU or CPUs while the hypervisor was servicing another virtual processor.

%idle

    Show the percentage of time that the CPU or CPUs were idle and the system did not have an outstanding disk I/O request.

Device Utilization Report
    The second report generated by the iostat command is the Device Utilization Report. The device report provides statistics on a per physical device or partition basis. Block devices for which statistics are to be displayed may be entered on the command line. Partitions may also be entered on the command line providing that option -x is not used. If no device nor partition is entered, then statistics are displayed for every device used by the system, and providing that the kernel maintains statistics for it. If the ALL keyword is given on the command line, then statistics are displayed for every device defined by the system, including those that have never been used. The report may show the following fields, depending on the flags used:

    Device:

            This column gives the device (or partition) name, which is displayed as hdiskn with 2.2 kernels, for the nth device. It is displayed as devm-n with 2.4 kernels, where m is the major number of the device, and n a distinctive number. With newer kernels, the device name as listed in the /dev directory is displayed.

tps

    Indicate the number of transfers per second that were issued to the device. A transfer is an I/O request to the device. Multiple logical requests can be combined into a single I/O request to the device. A transfer is of indeterminate size.

Blk_read/s

    Indicate the amount of data read from the device expressed in a number of blocks per second. Blocks are equivalent to sectors with kernels 2.4 and later and therefore have a size of 512 bytes. With older kernels, a block is of indeterminate size.

Blk_wrtn/s

    Indicate the amount of data written to the device expressed in a number of blocks per second.

Blk_read

    The total number of blocks read.

Blk_wrtn

    The total number of blocks written.

kB_read/s

    Indicate the amount of data read from the device expressed in kilobytes per second.

kB_wrtn/s

    Indicate the amount of data written to the device expressed in kilobytes per second.

kB_read

    The total number of kilobytes read.

kB_wrtn

    The total number of kilobytes written.

MB_read/s

    Indicate the amount of data read from the device expressed in megabytes per second.

MB_wrtn/s

    Indicate the amount of data written to the device expressed in megabytes per second.

MB_read

    The total number of megabytes read.

MB_wrtn

    The total number of megabytes written.

rrqm/s

    The number of read requests merged per second that were queued to the device.

wrqm/s

    The number of write requests merged per second that were queued to the device.

r/s

    The number of read requests that were issued to the device per second.

w/s

    The number of write requests that were issued to the device per second.

rsec/s

    The number of sectors read from the device per second.

wsec/s

    The number of sectors written to the device per second.

rkB/s

    The number of kilobytes read from the device per second.

wkB/s

    The number of kilobytes written to the device per second.

rMB/s

    The number of megabytes read from the device per second.

wMB/s

    The number of megabytes written to the device per second.

avgrq-sz

    The average size (in sectors) of the requests that were issued to the device.

avgqu-sz

    The average queue length of the requests that were issued to the device.

await

    The average time (in milliseconds) for I/O requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them.

svctm

    The average service time (in milliseconds) for I/O requests that were issued to the device. Warning! Do not trust this field any more. This field will be removed in a future sysstat version.

%util

    Percentage of CPU time during which I/O requests were issued to the device (bandwidth utilization for the device). Device saturation occurs when this value is close to 100%.

Network Filesystem report
    The Network Filesystem (NFS) report provides statistics for each mounted network filesystem. The report shows the following fields:

    Filesystem:

            This columns shows the hostname of the NFS server followed by a colon and by the directory name where the network filesystem is mounted.

rBlk_nor/s

    Indicate the number of blocks read by applications via the read(2) system call interface. A block has a size of 512 bytes.

wBlk_nor/s

    Indicate the number of blocks written by applications via the write(2) system call interface.

rBlk_dir/s

    Indicate the number of blocks read from files opened with the O_DIRECT flag.

wBlk_dir/s

    Indicate the number of blocks written to files opened with the O_DIRECT flag.

rBlk_svr/s

    Indicate the number of blocks read from the server by the NFS client via an NFS READ request.

wBlk_svr/s

    Indicate the number of blocks written to the server by the NFS client via an NFS WRITE request.

rkB_nor/s

    Indicate the number of kilobytes read by applications via the read(2) system call interface.

wkB_nor/s

    Indicate the number of kilobytes written by applications via the write(2) system call interface.

rkB_dir/s

    Indicate the number of kilobytes read from files opened with the O_DIRECT flag.

wkB_dir/s

    Indicate the number of kilobytes written to files opened with the O_DIRECT flag.

rkB_svr/s

    Indicate the number of kilobytes read from the server by the NFS client via an NFS READ request.

wkB_svr/s

    Indicate the number of kilobytes written to the server by the NFS client via an NFS WRITE request.

rMB_nor/s

    Indicate the number of megabytes read by applications via the read(2) system call interface.

wMB_nor/s

    Indicate the number of megabytes written by applications via the write(2) system call interface.

rMB_dir/s

    Indicate the number of megabytes read from files opened with the O_DIRECT flag.

wMB_dir/s

    Indicate the number of megabytes written to files opened with the O_DIRECT flag.

rMB_svr/s

    Indicate the number of megabytes read from the server by the NFS client via an NFS READ request.

wMB_svr/s

    Indicate the number of megabytes written to the server by the NFS client via an NFS WRITE request.

ops/s

    Indicate the number of operations that were issued to the filesystem per second.

rops/s

    Indicate the number of 'read' operations that were issued to the filesystem per second.

wops/s

    Indicate the number of 'write' operations that were issued to the filesystem per second.

Options

-c
    Display the CPU utilization report. 
-d
    Display the device utilization report. 
-h
    Make the NFS report displayed by option -n easier to read by a human. 
-k
    Display statistics in kilobytes per second instead of blocks per second. Data displayed are valid only with kernels 2.4 and later. 
-m
    Display statistics in megabytes per second instead of blocks or kilobytes per second. Data displayed are valid only with kernels 2.4 and later. 
-N
    Display the registered device mapper names for any device mapper devices. Useful for viewing LVM2 statistics. 
-n
    Display the network filesystem (NFS) report. This option works only with kernel 2.6.17 and later. 
-p [ { device [,...] | ALL } ]
    The -p option displays statistics for block devices and all their partitions that are used by the system. If a device name is entered on the command line, then statistics for it and all its partitions are displayed. Last, the ALL keyword indicates that statistics have to be displayed for all the block devices and partitions defined by the system, including those that have never been used. Note that this option works only with post 2.5 kernels. 
-t
    Print the time for each report displayed. The timestamp format may depend on the value of the S_TIME_FORMAT environment variable (see below). 
-V
    Print version number then exit. 
-x
    Display extended statistics. This option works with post 2.5 kernels since it needs /proc/diskstats file or a mounted sysfs to get the statistics. This option may also work with older kernels (e.g. 2.4) only if extended statistics are available in /proc/partitions (the kernel needs to be patched for that). 
-z
    Tell iostat to omit output for any devices for which there was no activity during the sample period.

Environment
The iostat command takes into account the following environment variable:

S_TIME_FORMAT
    If this variable exists and its value is ISO then the current locale will be ignored when printing the date in the report header. The iostat command will use the ISO 8601 format (YYYY-MM-DD) instead. The timestamp displayed with option -t will also be compliant with ISO 8601 format.

[emanuc]

Segnalo questa APP: https://flathub.org/apps/com.leinardi.gst

Features


Run different CPU and memory stress tests
Run multi and single core benchmark
Show Processor information (name, cores, threads, family, model, stepping, flags,bugs, etc)
Show Processor's cache information
Show Motherboard information (vendor, model, bios version, bios date, etc)
Show RAM information (size, speed, rank, manufacturer, part number, etc)
Show CPU usage (core %, user %, load avg, etc)
Show Memory usage
Show CPU's physical's core clock (current, min, max)
Show Hardware monitor (info provided by sys/class/hwmon)

https://gitlab.com/leinardi/gst#-features