Closed iblazhko closed 1 year ago
Why have you added the ESDB v5 in the docker compose file if it is not used?
As I mentioned in the README, I use the same Docker Compose file to run integration tests, and they require both V5 and V21/V22 instances.
Probably could move the esdb_v5_v22.yml
docker compose file out of Benchmark, and use it everywhere, including the build workflows, but it is for another PR.
Added benchmark test for stream loading and state re-hydration.
The test includes complete operation - opening BO session, reading event stream from ESDB, re-hydrating state. Because of that, it can be difficult to isolate effects and interpret results.
Nevertheless, it is a very useful test to have IMO.
Regarding
3.0.0-alpha23
vs3.0.0-alpha21
- test does not show that much of a difference in total memory consumption, but this may be due to the test design. There is however a noticeable improvement in Gen1/Gen2 GC numbers in test runs where we have very long event streams (see rows for 20000 and 50000 events) -3.0.0-alpha23
test run does not show any Gen2 GC collections which is very nice.Results
BullOak.EventStore
3.0.0-alpha23BullOak.EventStore
3.0.0-alpha21