]> git.proxmox.com Git - pmg-docs.git/blame_incremental - pmgperf.adoc
bump version to 6.0-2
[pmg-docs.git] / pmgperf.adoc
... / ...
CommitLineData
1[[chapter_pmgperf]]
2ifdef::manvolnum[]
3pmgperf(1)
4==========
5:pmg-toplevel:
6
7NAME
8----
9
10pmgperf - Proxmox Simple Performance Benchmark
11
12
13SYNOPSIS
14--------
15
16include::pmgperf.1-synopsis.adoc[]
17
18
19DESCRIPTION
20-----------
21endif::manvolnum[]
22ifndef::manvolnum[]
23pmgperf - Proxmox Simple Performance Benchmark
24==============================================
25:pmg-toplevel:
26endif::manvolnum[]
27
28The command line tool `pmgperf` tries to gather some general
29performance data. This is mostly useful for debugging and to identify
30performance bottlenecks. It computes the following metrics:
31
32[horizontal]
33CPU BOGOMIPS:: bogomips sum of all CPUs
34
35REGEX/SECOND:: regular expressions per second (perl performance
36 test), should be above 1000000.
37
38HD SIZE:: harddisk size
39
40BUFFERED READS:: simple HD read test. Modern HDs should reach at
41least 100 MB/sec
42
43AVERAGE SEEK TIME:: tests average seek time. Fast SCSI HDs reach
44values < 8 milliseconds. Common IDE/SATA disks get values from 15 to
4520 ms. SSD seek times should be below 1ms.
46
47FSYNCS/SECOND:: value should be greater than 200 (you should enable
48'write back' cache mode on you RAID controller - needs a battery
49backed cache (BBWC)).
50
51DNS EXT:: average time to resolve an external DNS name
52
53DNS INT:: average time to resolve a local DNS name
54
55Here is an example output generated by the tool:
56
57----
58# pmgperf
59CPU BOGOMIPS: 16759.60
60REGEX/SECOND: 1186304
61HD SIZE: 60.78 GB (/dev/sda1)
62BUFFERED READS: 209.84 MB/sec
63AVERAGE SEEK TIME: 1.24 ms
64FSYNCS/SECOND: 2198.79
65DNS EXT: 35.69 ms
66DNS INT: 1.41 ms (yourdomain.tld)
67----
68
69ifdef::manvolnum[]
70include::pmg-copyright.adoc[]
71endif::manvolnum[]
72