Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #51803
| Path | csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!newsfeed.xs4all.nl!newsfeed4.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail |
|---|---|
| Return-Path | <python.list@tim.thechases.com> |
| X-Original-To | python-list@python.org |
| Delivered-To | python-list@mail.python.org |
| X-Spam-Status | OK 0.125 |
| X-Spam-Level | * |
| X-Spam-Evidence | '*H*': 0.75; '*S*': 0.00; 'subject:Python': 0.06; 'dns,': 0.09; 'cc:addr:python-list': 0.11; 'python': 0.11; '-tkc': 0.16; 'erlang.': 0.16; 'from:addr:python.list': 0.16; 'from:addr:tim.thechases.com': 0.16; 'from:name:tim chase': 0.16; 'internally': 0.16; 'language?': 0.16; 'mean,': 0.16; 'wrote:': 0.18; 'passing': 0.19; 'programming': 0.22; '(in': 0.22; 'cc:addr:python.org': 0.22; 'load': 0.23; 'cc:2**0': 0.24; 'script': 0.25; 'permission': 0.26; 'second': 0.26; 'least': 0.26; 'gets': 0.27; 'header:In-Reply-To:1': 0.27; 'rest': 0.29; 'possibility': 0.29; "doesn't": 0.30; 'nature': 0.30; 'said,': 0.30; "i'm": 0.30; '(which': 0.31; 'text': 0.33; 'connection': 0.35; 'rate.': 0.36; 'smtp': 0.36; 'done': 0.36; 'charset:us- ascii': 0.36; 'should': 0.36; 'two': 0.37; 'depends': 0.38; 'handle': 0.38; 'little': 0.38; 'does': 0.39; 'volume': 0.39; 'simple,': 0.60; 'course': 0.61; 'simple': 0.61; "you're": 0.61; 'guarantee': 0.63; 'day.': 0.63; 'more': 0.64; '2000': 0.65; 'gathering': 0.68; 'steady': 0.68; 'email,': 0.69; 'emails,': 0.69; 'hour': 0.70; 'inline': 0.74; 'analysis': 0.75; 'day': 0.76; 'high,': 0.84; 'queued': 0.84; 'received:50.22': 0.84; "they'd": 0.84; 'mails': 0.89; 'destination': 0.91 |
| Date | Fri, 2 Aug 2013 07:59:26 -0500 |
| From | Tim Chase <python.list@tim.thechases.com> |
| To | Schneider <js@globe.de> |
| Subject | Re: Python performance |
| In-Reply-To | <51FB9F49.9040209@globe.de> |
| References | <51FB9F49.9040209@globe.de> |
| X-Mailer | Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu) |
| Mime-Version | 1.0 |
| Content-Type | text/plain; charset=US-ASCII |
| Content-Transfer-Encoding | 7bit |
| X-AntiAbuse | This header was added to track abuse, please include it with any abuse report |
| X-AntiAbuse | Primary Hostname - boston.accountservergroup.com |
| X-AntiAbuse | Original Domain - python.org |
| X-AntiAbuse | Originator/Caller UID/GID - [47 12] / [47 12] |
| X-AntiAbuse | Sender Address Domain - tim.thechases.com |
| X-Get-Message-Sender-Via | boston.accountservergroup.com: none |
| Cc | "python-list@python.org" <python-list@python.org> |
| X-BeenThere | python-list@python.org |
| X-Mailman-Version | 2.1.15 |
| Precedence | list |
| List-Id | General discussion list for the Python programming language <python-list.python.org> |
| List-Unsubscribe | <http://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe> |
| List-Archive | <http://mail.python.org/pipermail/python-list/> |
| List-Post | <mailto:python-list@python.org> |
| List-Help | <mailto:python-list-request@python.org?subject=help> |
| List-Subscribe | <http://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.121.1375448283.1251.python-list@python.org> (permalink) |
| Lines | 44 |
| NNTP-Posting-Host | 2001:888:2000:d::a6 |
| X-Trace | 1375448283 news.xs4all.nl 16007 [2001:888:2000:d::a6]:43033 |
| X-Complaints-To | abuse@xs4all.nl |
| Xref | csiph.com comp.lang.python:51803 |
Show key headers only | View raw
On 2013-08-02 14:00, Schneider wrote: > I have to write a small SMTP-Relay script (+ some statistic infos) > and I'm wondering, if this > can be done in python (in terms of performance, of course not in > terms of possibility ;) ). > > It has to handle around 2000 mails per hour for at least 8hours a > day (which does not mean, that it is allowed not to respond the > rest of the day. > > Can this be done? or should I better use some other programming > language? My second choice would be erlang. I suspect it depends on a lot of factors: - will your network connection support that much traffic? (And an ISP that will grant you permission to spew that volume of email?) - are these simple text emails, or are they large with lots of attachments, inline images, PDFs, or whatever? - are the statistics that you're gathering simple, or do they require complex analysis of the documents passing through? - is the load 8hr straight of spewing email, or is it bursty? If it's bursty, you can internally queue them up when load gets high, delivering them from that queue when load diminishes. Given the store-and-forward nature of email, there's no guarantee that if you spewed them at ~33/minute (that/s a little faster than one every two seconds), they'd arrive at their destination any faster than if you'd queued them up and sent them at a more steady rate. That said, sending ~33 text emails per minute doesn't seem impossible, it just depends on your configuration (network, DNS, and receiving SMTP server(s) throttling/setup) -tkc
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Python performance Tim Chase <python.list@tim.thechases.com> - 2013-08-02 07:59 -0500
csiph-web