2 reports
Measured 2026-10-09 · 2 rounds of testing
Does a huge product catalogue slow things down?
With 3.3 million products in the catalogue, does saving items, scanning codes or searching for products get slower?
Measured 2026-10-07
How fast is counting and checking stock?
Can one team keep uploading while its supervisor watches progress, and does that keep working as the job fills up?
How to read these
Every number came from a measurement. After each test the team went back to the stored data and counted what was really written or read, and the report only counts a test that matched. Slow results were re-measured before being called a problem.
- "9 out of 10" is the honest way to quote a wait. It is the wait that nine people out of ten experienced, so one unusually slow moment does not distort it.
- A factor is only stated when it repeated. Anything that looked slow on the first pass was measured again before the report claims a problem.
- These are not promises about our cloud servers. The numbers come from the test machine described in each report, and each report says what it did not test.
| Measured | Report | Cases | Time | Result |
|---|---|---|---|---|
| 2026-10-09 | Does a huge product catalogue slow things down? | 103 | 45 min | all checks passed |
| 2026-10-07 | How fast is counting and checking stock? | 73 | not recorded | all checks passed |
What is behind these reports
- Does a huge product catalogue slow things down? — numbers from
tests/performance/20261009-products/reports - How fast is counting and checking stock? — numbers from
tests/performance/20261008-baseline-write-read/reports
The pages above are standalone files: they open from disk with no internet connection and no server. This index and every report it links to can be uploaded together as one folder.