|Anonymous | Login | Signup for a new account||2019-10-17 06:31 EDT|
|My View | View Issues | Change Log | Roadmap | Repositories|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0004779||SOGo||Web Mail||public||2019-07-12 04:00||2019-09-12 09:54|
|Priority||normal||Severity||feature||Reproducibility||have not tried|
|Platform||[Server] Linux||OS||Debian||OS Version||8 (Jessie)|
|Target Version||Fixed in Version|
|Summary||0004779: Instantly show new mails / IMAP Notify support|
|Description||SOGo seems to poll for new messages. As the min poll time is 1 Minute this adds in average 30 seconds of delay i guess.|
Would be nice if it supports IMAP NOTIFY to instantly show new messages.
When logged in via SOGo webmail and Thunderbird, Thunderbird always shows new mails before SOGo notifies about it.
|Additional Information||https://tools.ietf.org/html/rfc5465 [^]|
|Tags||No tags attached.|
it looks like SOGo logins and logouts for every request to the IMAP server.
IMHO this would require a permanent connection to the IMAP server of sogo.
very likely when this is implemented 0004789 would be fixed, too.
Did i miss a possibility to configure SOGo, so it keeps a connection to the IMAP server for better Performance?
Christian Mack (developer)
edited on: 2019-09-06 08:40
Keeping one connection per logged in user is a resource problem.
For installations with a couple of users that would be possible.
But for installations with hundreds or thousands of concurrently logged in users that would be a no go.
On our installation (approx. 20.000 users; 800+ concurrent users) we even have restricted polling to 5 minutes or longer.
No complaints so far.
> Keeping one connection per logged in user is a resource problem.
which resource would be the limiting factor? memory? sockets? file handles?
on our installation (approx. 200 users) we had complains about the delay :-|
Christian Mack (developer)
In SOGo each persistant connection would use up one worker, like ActiveSync.
That means it uses up to SxVMemLimit of RAM per user.
Default for SxVMemLimit is 384 MB.
For 200 users this means 75 GB RAM max for SOGo alone.
You realistically need half of it for peak load.
That means you need a machine with more than 37 GB of RAM, as you need some for OS, memcached, database and your reverse proxy too.
Beware, that is for 200 clients.
But each user has normally at least 2 clients (computer/laptop and smartphone/tablet).
With that in mind, only half of your users can be concurrently online.
Or you have to provide even more RAM.
|2019-07-12 04:00||abma||New Issue|
|2019-08-30 11:50||abma||Note Added: 0013725|
|2019-09-06 08:39||Christian Mack||Note Added: 0013731|
|2019-09-06 08:40||Christian Mack||Note Edited: 0013731||View Revisions|
|2019-09-06 17:18||abma||Note Added: 0013733|
|2019-09-09 03:31||Christian Mack||Note Added: 0013734|
|Copyright © 2000 - 2019 MantisBT Team|