[prev in list] [next in list] [prev in thread] [next in thread] 

List:       twsocket
Subject:    Re: [twsocket] Optimal number of TWSocket per thread
From:       "Max Terentiev" <maxterentiev () mail ! ru>
Date:       2012-11-07 18:47:23
Message-ID: 000601cdbd18$541b9150$fc52b3f0$ () ru
[Download RAW message or body]

Arno,

It's should be optimized anyway because multipart/alternative
messages can be relatively large (20-30 kb of html+text+headers).

To send this message current implementation perform about
320 calls to DataNext. While optimized - only 20 calls.

For high load smtp relay it's a VERY big difference. 

Right now I playing with enlarging send buffer... With 900 bytes
length I see about 300% of speed increase (from 200 megabytes/sec
to 600 megabytes/sec).

---
With best regards, Max Terentiev.
Business Software Products.
AMS Development Team.
support@bspdev.com

-----Original Message-----
From: twsocket-bounces@elists.org [mailto:twsocket-bounces@elists.org] On
Behalf Of Arno Garrels
Sent: Wednesday, November 07, 2012 10:31 PM
To: ICS support mailing
Subject: Re: [twsocket] Optimal number of TWSocket per thread

Max Terentiev wrote:
> Hi Angus,
> 
> I perform some tests but cannot send fasten than 200 megabit/sec.
> 
> On large messages (100kb+) Looks like a bottleneck in SmtpCli's 
> Data/DataNext function.
> 
> I see the code and found what DataNext send message line by line.

You are right, that's indeed some bottleneck. I already changed that for
attachments some months ago. On the other side, it's unlikely that a message
body will contain plenty of lines.
   
--
Arno
--
To unsubscribe or change your settings for TWSocket mailing list please goto
http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
[prev in list] [next in list] [prev in thread] [next in thread]