From: Malte S. <m...@ma...> - 2024-07-11 14:28:14
|
Hello, I am currently in the process of evaluating solutions to decrease latency in a webmail based IMAP setup. imapproxy was one of my approaches. In a test environment, I set it up with imaptest for generating a specific workload with a specific amount. Lets say 100 users with 5 sessions each. They connect to imapproxy which then connects over a higher-latency network to the IMAP server. In my testcase, with the following config, I saw a buildup of connections until the IMAP server reached a max-client-limit of 1000. From my understanding this is not how the imapproxy was meant - shouldnt it have build up 100 connections (because there are only 100 unique users) and then kept them open, sending commands via them? Meaning that even a LOGOUT would not cause the connection to abort, because it will later be reused for other IMAP commands? server_hostname {{ host }} connect_retries 10 connect_delay 5 cache_size 30720 listen_port 143 listen_address 0.0.0.0 cache_expiration_time 300 send_tcp_keepalives yes enable_select_cache no server_port 143 proc_username nobody proc_groupname nogroup protocol_log_filename /var/log/prtc stat_filename /var/log/stats foreground_mode yes Excuse my somewhat strange attempt at reviving this dead mailinglist. Appreciate any helpful inputs! Best regards |