WalterH There is a great and informative explanation about mailbox performance and how the developers have increased performance with recent community updates. Please read this article: https://grommunio.com/news/grommunio-improves-mailbox-performance/ Also read the change log: https://github.com/grommunio/gromox/commit/f0a485f5498dbe843f1b101807dd063edce02036
rgfatter I used to have sometimes unusal waiting times for messages to load in the webinterface. (community version, single user installation, ActiveSync, etc. has always been smooth) With the latest update installed, these performance drops in the webinterface seem to have gone for good. Thank you!
ChrisH Just out of curiosity: Why were the locking mechanisms provided by SQLite not enough so you had to wrap an additional locking layer around those (and then a clumsy one like a mutex even for read access)? Controlling concurrent access is a classic database engine problem, the application should not have to worry about it. It looks to me that SQLite had that pretty well handled even in the old version 3.0: https://www.sqlite.org/lockingv3.html https://www.sqlite.org/wal.html So what is Grommunio doing differently? (I'm a SQL server guy myself, but I'm always willing to learn something new 🙂 )
WalterH ChrisH https://www.sqlite.org/wal.html I am not the developer but I knew, Write-Ahead Logging is used by grommunio.