Johan Bjäreholt

> We need to be able to create instances of the database that do not migrate/update like the local instance does (to ensure that they are readable by versions of...

Maybe also make a unique identifier for each computer? Or should we continue using hostname and simply refuse if two machines have the same hostname? I'd prefer using hostname because...

I realized that the whole mpsc thread model is a bit excessive if we are to only have read access to the database, so I rewrote the datastore code to...

> We need to be able to create instances of the database that do not migrate/update like the local instance does (to ensure that they are readable by versions of...

> I appreciate it, but I kinda think that the solution you proposed was better (and is how Syncthing deals with nodes of different versions) If you look at the...

@ErikBjare After I benchmarked #183 I realized that memory copying was incredibly fast already and the improvement was still barely noticeable in an extreme benchmark scenario I made up. I...

Apparently the calculate_endtime() function is incredibly slow, I was able to do a 5x optimization by caching the endtime for the filter events in each loop. Will push a PR...

Same query on exact same data in the web-ui in the above example went from 13.3 seconds to 7.53 seconds where the big filter_period_intersect went from 6.78 seconds to 1.24...

Wrapping our event lists in allocation arenas should significantly improve memory usage, would probably completely fix the "leak-like" behavior of the allocator keeping a lot more memory after big queries...

We could split up aw-server-rust into aw_datastore, aw_core, aw_transform into packages and have a aw_server package which uses all these then add a "python" feature and add bindings with https://github.com/PyO3/pyo3...