The test performs a massively concurrent scenario that presses with 100 threads and 1 MiB allocation for each. This highlighted my still limited understanding of the situation and leads to a much better solution, where, on-demand, some worker performs all the accrued allocation and management work. So effectively we do not even need to use the synchronous API |
||
|---|---|---|
| .. | ||
| buffer-metadata-key-test.cpp | ||
| buffer-metadata-test.cpp | ||
| buffer-provider-protocol-test.cpp | ||
| buffer-proxy-adaptor-test.cpp | ||
| buffer-store-test.cpp | ||
| diagnostic-buffer-provider-test.cpp | ||
| engine-buffer-manager-test.cpp | ||
| extent-family-test.cpp | ||
| local-buffer-stage-test.cpp | ||
| local-buffer-store-test.cpp | ||
| local-mem-pool-test.cpp | ||