Python Scalability TCP Server + Background Game

[phiwer at 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