Annotate
mod_benchmark_storage/README.markdown @ 4877:adc6241e5d16
mod_measure_process: Report the enforced limit
The soft limit is what the kernel actually enforces, while the hard
limit is is how far you can change the soft limit without privileges.
Unless the process dynamically adjusts the soft limit, knowing the hard
limit is not as useful as knowing the soft limit.
Reporting the soft limit and the number of in-use FDs allows placing
alerts on expressions like 'process_open_fds / process_max_fds >= 0.95'
| author |
Kim Alvefur <zash@zash.se> |
| date |
Tue, 18 Jan 2022 18:55:20 +0100 |
| parent |
1857:5a19ccd8457a |
| rev |
line source |
|
1857
|
1 ---
|
|
|
2 summary: Storage benchmark tool
|
|
|
3 ...
|
|
|
4
|
|
|
5 To benchmark `mod_storage_internal`:
|
|
|
6
|
|
|
7 prosodyctl mod_benchmark_storage internal
|
|
|
8
|
|
|
9 Does a number (aprox. 10000) of reads and writes and to the selected
|
|
|
10 storage driver and tells you how long it took.
|
