annotate mod_benchmark_storage/README.markdown @ 4065:92152437ecfe

mod_muc_markers: replace configurable multi-marker tracking with better system Now tracks a single marker, but automatically applies rules from the XEP about "higher" markers implying "lower" markers - i.e. "displayed" implies "received". Still, just a single marker is tracked and synthesized at all times (the one configured with muc_marker_name).
author Matthew Wild <mwild1@gmail.com>
date Tue, 07 Jul 2020 17:08:08 +0100
parents 5a19ccd8457a
children
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
rev   line source
1857
5a19ccd8457a mod_benchmark_storage: Add README
Kim Alvefur <zash@zash.se>
parents:
diff changeset
1 ---
5a19ccd8457a mod_benchmark_storage: Add README
Kim Alvefur <zash@zash.se>
parents:
diff changeset
2 summary: Storage benchmark tool
5a19ccd8457a mod_benchmark_storage: Add README
Kim Alvefur <zash@zash.se>
parents:
diff changeset
3 ...
5a19ccd8457a mod_benchmark_storage: Add README
Kim Alvefur <zash@zash.se>
parents:
diff changeset
4
5a19ccd8457a mod_benchmark_storage: Add README
Kim Alvefur <zash@zash.se>
parents:
diff changeset
5 To benchmark `mod_storage_internal`:
5a19ccd8457a mod_benchmark_storage: Add README
Kim Alvefur <zash@zash.se>
parents:
diff changeset
6
5a19ccd8457a mod_benchmark_storage: Add README
Kim Alvefur <zash@zash.se>
parents:
diff changeset
7 prosodyctl mod_benchmark_storage internal
5a19ccd8457a mod_benchmark_storage: Add README
Kim Alvefur <zash@zash.se>
parents:
diff changeset
8
5a19ccd8457a mod_benchmark_storage: Add README
Kim Alvefur <zash@zash.se>
parents:
diff changeset
9 Does a number (aprox. 10000) of reads and writes and to the selected
5a19ccd8457a mod_benchmark_storage: Add README
Kim Alvefur <zash@zash.se>
parents:
diff changeset
10 storage driver and tells you how long it took.