That’s probably because you were using RocksDB as a backend, which does not work well on mechanical HDDs. Try using PostgreSQL instead.
Comment on Introducing Calendars, Contacts and Files in Stalwart | Stalwart Labs
Shimitar@downonthestreet.eu 4 weeks ago
I had to give up on stalwart because on 4gb ram dual core with mechanical HDD the performance for a single account domain was abysmal and after some support back and forth there was no solution.
On the same hardware the good old postfix+dovecot just handles perfectly with 90% spare capacity
Sorry guys, maybe it was time to optimize it a bit before adding more features?
stalwartlabs@lemmy.world 4 weeks ago
Shimitar@downonthestreet.eu 4 weeks 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.
warmaster@lemmy.world 4 weeks ago
They have improved performance in this release, although judging from their release notes it is targeting larger infra, so I don’t believe these improvements would benefit your setup. Still, good news for software this new.
abeorch@friendica.ginestes.es 4 weeks ago
@warmaster @Shimitar Their licencing suggests they are targetting larger infra.warmaster@lemmy.world 4 weeks ago
Yeah, that’s what I said in the post you’re replying to. Is this a case of weird cross-platform federation?
abeorch@friendica.ginestes.es 4 weeks ago
@warmaster I was just agreeding and suggesting that their monetisation strategy is licencing hence the reason for improvements for Enterprise clusters rather than focusing on Self Hosting is the money.
aksdb@lemmy.world 4 weeks ago
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.
Shimitar@downonthestreet.eu 4 weeks ago
Stalwart probably aims a bigger infra than mine, i think that is the point.
aksdb@lemmy.world 4 weeks ago
It aims at both, otherwise it wouldn’t ship with sqlite and rocksdb. Stalwarts default is clearly for single node setups and expanding it to clustering takes further steps. So while it supports large scale deployments, it should not be limited to it.
victorz@lemmy.world 4 weeks ago
Are we sure they are using semantic versioning?
aksdb@lemmy.world 4 weeks ago
We can ask, but the indicators are there:
victorz@lemmy.world 4 weeks ago
Mm, interesting.