Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #75434
| Path | csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.fsmpi.rwth-aachen.de!rt.uk.eu.org!newsfeed.xs4all.nl!newsfeed3a.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail |
|---|---|
| Return-Path | <charleshixsn@earthlink.net> |
| X-Original-To | python-list@python.org |
| Delivered-To | python-list@mail.python.org |
| X-Spam-Status | OK 0.030 |
| X-Spam-Evidence | '*H*': 0.94; '*S*': 0.00; 'receives': 0.04; 'json': 0.07; 'tcp/ip': 0.09; 'runs': 0.10; 'message-id:@earthlink.net': 0.16; 'otoh,': 0.16; 'peer-to-peer': 0.16; 'received:dsl.mindspring.com': 0.16; 'subject:skip:m 10': 0.16; 'tradeoffs': 0.16; 'seems': 0.21; 'input': 0.22; 'header:User- Agent:1': 0.23; "i've": 0.25; "i'm": 0.30; 'easier': 0.31; 'figure': 0.32; 'guess': 0.33; 'noticed': 0.34; 'could': 0.34; 'received:66': 0.35; 'something': 0.35; 'to:addr:python-list': 0.38; 'to:addr:python.org': 0.39; 'either': 0.39; 'telling': 0.64; 'more': 0.64; 'management': 0.65; '(that': 0.65; 'subject:. ': 0.67; 'between': 0.67; 'grow': 0.77; 'bite': 0.84 |
| Date | Thu, 31 Jul 2014 12:00:43 -0700 |
| From | Charles Hixson <charleshixsn@earthlink.net> |
| User-Agent | Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.5.0 |
| MIME-Version | 1.0 |
| To | python-list@python.org |
| Subject | multiprocessing vs. asyncio.SubprocessProtocol |
| Content-Type | text/plain; charset=ISO-8859-1; format=flowed |
| Content-Transfer-Encoding | 7bit |
| 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 | <https://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 | <https://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.12482.1406833433.18130.python-list@python.org> (permalink) |
| Lines | 16 |
| NNTP-Posting-Host | 2001:888:2000:d::a6 |
| X-Trace | 1406833433 news.xs4all.nl 2941 [2001:888:2000:d::a6]:37600 |
| X-Complaints-To | abuse@xs4all.nl |
| Xref | csiph.com comp.lang.python:75434 |
Show key headers only | View raw
What are the tradeoffs between using multiprocessing vs. using asyncio.SubprocessProtocol? This only one that I've noticed is that asyncio seems to require much more hands-on management of message queueing. OTOH, I'm no expert in either of them, and I might be missing something that will bite me later. OTOH, I could do the whole thing with a TCP/IP peer-to-peer setup on localhost. And that's much easier to figure out. (Each process has one input queue, and runs until it receives a message telling it to die. JSON is all I need for serialization...though ast.literal_eval would work as well.) So I guess I also want to know whether there's any advantage in using multiprocessing vs using a datagram transmission over localhost. (That clearly has the advantage that it makes it easier to grow to multiple machines.)
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
multiprocessing vs. asyncio.SubprocessProtocol Charles Hixson <charleshixsn@earthlink.net> - 2014-07-31 12:00 -0700
csiph-web