[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.0.98.0705071101510.6512@sigma.j-a-k-j.com>
Date: Mon, 7 May 2007 11:03:54 -0400 (EDT)
From: "John Anthony Kazos Jr." <jakj@...-k-j.com>
To: Matti Aarnio <matti.aarnio@...iler.org>
cc: linux-kernel@...r.kernel.org
Subject: Re: gmail is a bit too popular..
> In the linux-kernel -list subscribers domain popularity
> analysis I got following results:
>
> 2101 gmail.com
> 49 googlemail.com
> 46 gmx.de
> 41 redhat.com
> 33 yahoo.com
> 23 suse.de
> 22 gmx.net
> 21 comcast.net
>
>
> The gmail is so popular, that with their somewhat rudimentary
> inbound MTA software this kind of recipient masses take horrible
> time to feed in... Mere 0.5-0.7 seconds per recipient, but..
>
> So far we have tried to feed all recipients in one go per
> message - that is sending 2100 RCPT TO -lines in one swoop,
> and the system has taken some 15-25 minutes per message to
> feed it to gmail. We are running the delivery 20 streams in
> parallel, so it isn't quite as bad as it sounds..
>
> I do have one thing that gmail could enable to speed up the message
> delivery (a lot!) from VGER and other list delivery sources.
> That single magic needed thing is called "PIPELINING" support
> at gmail's inbound MX servers. With suitably well behaving
> smtpserver it is really trivial to implement, all real difficult
> magic is at the sending side smtp client codes.
>
> Once upon a time I implemented that thing for a trans-atlantic
> SMTP fanout feed -- message delivery time became slashed from
> hundreds of RTT delays to mere few..
How about some elitism here? Dedicate a certain number of streams to
everything-except-gmail, so MTAs from the 21st century can get their mail
faster, and set the rest on gmail-only. Slows down gmail and speeds up the
rest?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists