ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ's avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ me@mleku.dev 2 months ago
you can already test it yourself if you have docker compose installed. see here:
Gitea
next.orly.dev/cmd/benchmark/README.md at main
next.orly.dev - Total rewrite of ORLY to simplify and make it more robust
 i am too impatient and busy actually optimizing orly to have sat through the hour long or so process it takes to run all of the benches, but this covers all of them, including now orly with dgraph, and neo4j is coming soon.
↑ Parent

Replies (1)

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ's avatar
ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ me@mleku.dev 2 months ago
actually the bench might be a bit broken at the moment because i'm adding neo4j now and i changed the event generator to create a distribution of sizes to be realistic, from about 300 bytes up to 500kb. currently you may find that the benchmark blows up memory and causes the benchmark runner to OOM kill because it's using so much memory on the test event sets. fixing that now, will bump an update shortly
↑