dshulyak commented 5 years ago

Status console client selects random mail server from a list of configured mail servers. It is clearly prone to network issues, i collected bandwidth stats from mailservers in 3 different regions:

bw stats

mail do beta

[ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 60.8 MBytes 51.0 Mbits/sec 202 sender [ 4] 0.00-10.00 sec 59.1 MBytes 49.6 Mbits/sec receiver

mail staging do

[ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 50.2 MBytes 42.1 Mbits/sec 235 sender [ 4] 0.00-10.00 sec 48.4 MBytes 40.6 Mbits/sec receiver

mail gc staging

[ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 15.4 MBytes 12.9 Mbits/sec 160 sender [ 4] 0.00-10.00 sec 13.6 MBytes 11.4 Mbits/sec receiver

hong-kong staging

[ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 7.11 MBytes 5.97 Mbits/sec 196 sender [ 4] 0.00-10.00 sec 5.25 MBytes 4.41 Mbits/sec receiver

Only mail servers from eu region can be used by me, any other mail server won't deliver history in reasonable time.

I suggest to move selection of the mail servers on the level of messenger and provide api to add/select/delete mail server. If no mail server is selected we will use random one, or in future do some bw testing before choosing mail servers.

cc @adambabik

adambabik commented 5 years ago

Maybe we can implement a mechanism that would try to select the nearest mailserver from a list if none is already selected? However, this should be in status-go rather than here.

I agree that we should have add/select/delete mailserver operations on the messenger.