| Event | Time (in addition to Confluence's algorithm). For ~400 requirements, 1Kb each in average, ~525Kb text per page, 2ms network latency. No Jira connection. | Time 1ms | database latency.Time 1ms latency,
200-char requirements Time 1ms latency,
1000 requirements |
|---|
| Page creation | - 400ms 480ms rendering of the page
- 48ms 22ms per requirement,
- Total: +19,6 8.9 seconds (on top of Confluence's algorithm).
- 400ms rendering
- 14ms per requirement,
- Total +6068ms.
| — | - 1082ms
rendering (Confluence) - 12ms 13ms per requirement
- Total +12324ms13s
|
| Page edition | - 400ms 700ms rendering of the page
- 32ms 21ms per requirement,
- Total +13,3 seconds.
For 0 requirement and 480kb of raw text: - 1ms if the page doesn't contain any "include" or "Scaffolding" macro,
- 564ms if the page contains mutable content (include macro or Scaffolding).
| - 400ms rendering
- 12ms per requirement,
- Total +5272ms.
| - 400ms rendering
- Total +4791ms.
| - 2081ms rendering
- 10ms per requirement
Total +12204ms- 11.6 seconds.
| - 1700ms rendering
- 15ms per requirement
- Total +15.7s
|
Submission of excerpts (This operation is in the background, the user doesn't wait for this). | - 4ms per non-modified requirement,
- 10 to 53ms 20-40ms per modified requirement,
(depending on the size of text and the number of properties). - Total 1218,800s 7s for 400 modified requirements.5,26ms
- Note: This is with 2ms additional network latency per DB queries. For most networks between a server and its database, the latency is sub-1ms.
| - 8ms per modified requirement,.
- Total +2107ms.
| | - 8ms per modified requirement.
- Total +8111ms8111ms
New result: - 3ms per modified requirement
- Total: 3s
60ms par requirement, c'est 60 requêtes. |
| Tested for Requirement Yogi 2.0.0 with 2ms and 1ms network latency, in addition to the database latency, already loaded with 80.000 requirements. |