It’s a 0.x release. It makes sense building the intended features first before optimizing heavily. There’s no point having an optimized data structure that then falls flat once you need to add new features that brings new requirements to the data structure.
Once they label it 1.x (i.e. feature complete and production ready) I would expect it to be optimized. If it isn’t, criticism is warranted.
stalwartlabs@lemmy.world 10 months ago
That’s probably because you were using RocksDB as a backend, which does not work well on mechanical HDDs. Try using PostgreSQL instead.
Shimitar@downonthestreet.eu 10 months ago
I did, we discussed this on an issue and a github discussion. It was still too slow and saturating my low spec machine, no matter which backends I tried to use.
Probably my hardware is just too underpowered.