Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #64225
| Newsgroups | comp.lang.python |
|---|---|
| Date | 2014-01-18 03:54 -0800 |
| References | <27bae268-20a6-4ac3-a0dc-bd5be04d1da1@googlegroups.com> <mailman.5544.1389820104.18130.python-list@python.org> <0ab89748-bce2-436f-a00b-41e8199430f6@googlegroups.com> <mailman.5670.1390032110.18130.python-list@python.org> |
| Message-ID | <fde71dc8-0152-41b8-8910-b4395a07a1d5@googlegroups.com> (permalink) |
| Subject | Re: Python Scalability TCP Server + Background Game |
| From | phiwer@gmail.com |
> (You're using Google Groups, which means your replies are > > double-spaced and your new text is extremely long lines. Please fix > > this, either by the fairly manual job of fixing every post you make, > > or the simple method of switching to a better client. Thanks.) > > > > My point was just about the REST API, nothing else. You have to handle > > a request and a response for every API call. Whether they're reads or > > writes, you need to receive an HTTP request and send an HTTP response > > for each one. In order to support the 50k requests per second you hope > > for, you would have to handle 50k requests coming in and 50k responses > > going out. To do that, you would need - at a very VERY rough estimate > > - a maximum request size of 2KB and a gigabit internet connection > > (which is expensive). No further calculations are worth pursuing if > > you can't handle those requests and responses. > > > > (And small requests tend to be more expensive than large ones. Since > > you'll need a minimum of >SYN, <SYN/ACK, >ACK, >DATA, <DATA, >FIN, > > <FIN/ACK, >ACK in order to transmit and receive one single packet's > > worth of data each way, you're looking at roughly 8 packets minimum > > for a one-byte message and one-byte response. But at a very very rough > > estimate, 2KB each direction is the most you can sustain.) > > > > ChrisA Aha, thanks for the info. But the assumptions you are making does not answer the question. And the question you raise, although important, is more a financial one, not really relevant to the questions I posed. Regards, Phil
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Python Scalability TCP Server + Background Game phiwer@gmail.com - 2014-01-15 10:37 -0800
Re: Python Scalability TCP Server + Background Game Chris Angelico <rosuav@gmail.com> - 2014-01-16 08:08 +1100
Re: Python Scalability TCP Server + Background Game phiwer@gmail.com - 2014-01-17 23:44 -0800
Re: Python Scalability TCP Server + Background Game Chris Angelico <rosuav@gmail.com> - 2014-01-18 19:01 +1100
Re: Python Scalability TCP Server + Background Game phiwer@gmail.com - 2014-01-18 03:54 -0800
Re: Python Scalability TCP Server + Background Game Asaf Las <roegltd@gmail.com> - 2014-01-18 04:13 -0800
Re: Python Scalability TCP Server + Background Game phiwer@gmail.com - 2014-01-18 04:40 -0800
Re: Python Scalability TCP Server + Background Game Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-01-18 13:19 +0000
Re: Python Scalability TCP Server + Background Game Philip Werner <phiwer@gmail.com> - 2014-01-19 12:53 -0600
Re: Python Scalability TCP Server + Background Game Chris Angelico <rosuav@gmail.com> - 2014-01-20 05:58 +1100
Re: Python Scalability TCP Server + Background Game Philip Werner <phiwer@gmail.com> - 2014-01-21 03:59 -0600
csiph-web