Re: [twsocket] TWSocket.Connet/GetHostByName bottleneck

2015-09-18 Thread Stephen Dickason
- From: TWSocket [mailto:twsocket-boun...@lists.elists.org] On Behalf Of Max Terentiev Sent: 18 September 2015 02:07 To: ICS support mailing Subject: [twsocket] TWSocket.Connet/GetHostByName bottleneck Hi, I develop smtp relay server using ICS. And I notice very big performance hit if many

Re: [twsocket] TWSocket.Connet/GetHostByName bottleneck

2015-09-18 Thread Angus Robertson - Magenta Systems Ltd
> At this time I see this way: > > 1. Use TDNSQuery.MXLookup to resolve MX, then TDNSQuery.ALookup to > resolve MX's IP. Then supply resolved MX IP to TSmtpCli to avoid > GetHostByName. > > 2. Cache both MX and A results in my own DNS cache. Seems sensible, just make sure you time out the

[twsocket] TWSocket.Connet/GetHostByName bottleneck

2015-09-17 Thread Max Terentiev
Hi, I develop smtp relay server using ICS. And I notice very big performance hit if many TSmtpCli's connects to remote MX server in parallel ! I use TDnsQuery to resolve domain's MX server then supply result to TSmtpCli. If I use 100+ TSmtpCli instances most of them waits for OnRequestDone