On 25-Jul-2010, at 5:52 PM, Roy Smith wrote:
> In article <4c4bd0b1$0$1624$742ec...@news.sonic.net>,
> John Nagle wrote:
>
>>1. When writing to a TCP socket, write everything you have to write
>>with one "send" or "write" operation if at all possible.
>>Don't write a little
In article <4c4bd0b1$0$1624$742ec...@news.sonic.net>,
John Nagle wrote:
> 1. When writing to a TCP socket, write everything you have to write
> with one "send" or "write" operation if at all possible.
> Don't write a little at a time. That results in sending small
>
On 7/23/2010 5:06 PM, Navkirat Singh wrote:
Hey Everyone,
I had a question, programming sockets, what are the things that would
degrade performance and what steps could help in a performance boost? I
would also appreciate being pointed to some formal documentation or
article.
1. When writ
On 25-Jul-2010, at 6:45 AM, Lawrence D'Oliveiro wrote:
> In message
> , Navkirat Singh wrote:
>
>> I had a question, programming sockets, what are the things that would
>> degrade performance and what steps could help in a performance boost?
>
> Remember the old saying, “premature optimization
In message
, Navkirat Singh wrote:
> I had a question, programming sockets, what are the things that would
> degrade performance and what steps could help in a performance boost?
Remember the old saying, “premature optimization is the root of all evil”.
Have you actually got some code working pr
Navkirat Singh wrote:
Thanks for the info : ). I will look into it ! Right now I am having a
strange problem. I am trying to use cookies and the import function
returns an error:
I am using python 3:
from http import cookies
*importError:* No module named http
Is it my configuration or has
Thanks for the info : ). I will look into it ! Right now I am having a
strange problem. I am trying to use cookies and the import function
returns an error:
I am using python 3:
from http import cookies
importError: No module named http
Is it my configuration or has something changed since
Navkirat Singh wrote:
Hey Everyone,
I had a question, programming sockets, what are the things that would
degrade performance and what steps could help in a performance boost? I
would also appreciate being pointed to some formal documentation or
article.
I am new to this.
Interleaving pro
On Mar 16, 1:29 pm, "Gabriel Genellina" <[EMAIL PROTECTED]>
wrote:
> En Sat, 15 Mar 2008 20:08:05 -0200, <[EMAIL PROTECTED]> escribi�:
>
>
>
>
>
> > On Mar 15, 8:18 am, Bryan Olson <[EMAIL PROTECTED]> wrote:
> >> [EMAIL PROTECTED] wrote:
> >> > Newbie question: Can you write to the 'file-like obje
En Sat, 15 Mar 2008 20:08:05 -0200, <[EMAIL PROTECTED]> escribi�:
> On Mar 15, 8:18 am, Bryan Olson <[EMAIL PROTECTED]> wrote:
>> [EMAIL PROTECTED] wrote:
>> > Newbie question: Can you write to the 'file-like object' a pickle,
>> > and receive it intact-- as one string with nothing else?
>>
>> Ye
On Mar 15, 8:18 am, Bryan Olson <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > Gabriel Genellina wrote:
> >> No need to reinvent the wheel. socket objects already have a makefile
> >> method returning a file-like object, which behaves like a buffered socket.
>
> That wheel is far from
[EMAIL PROTECTED] wrote:
> Gabriel Genellina wrote:
>> No need to reinvent the wheel. socket objects already have a makefile
>> method returning a file-like object, which behaves like a buffered socket.
That wheel is far from round, and needs some reinvention. Python's
file-like objects do not p
On Mar 15, 3:33 am, "Gabriel Genellina" <[EMAIL PROTECTED]>
wrote:
> En Thu, 13 Mar 2008 15:18:44 -0200, <[EMAIL PROTECTED]> escribió:
>
> > Well, lets say you have a situation where you're going to be
> > alternating between sending large and small chunks of data. Is the
> > solution to create a N
En Thu, 13 Mar 2008 15:18:44 -0200, <[EMAIL PROTECTED]> escribió:
> Well, lets say you have a situation where you're going to be
> alternating between sending large and small chunks of data. Is the
> solution to create a NetworkBuffer class and only call send when the
> buffer is full, always recv
[EMAIL PROTECTED] wrote:
> Well, lets say you have a situation where you're going to be
> alternating between sending large and small chunks of data. Is the
> solution to create a NetworkBuffer class and only call send when the
> buffer is full, always recv(8192)?
Buffering can often improve perfo
[EMAIL PROTECTED] wrote:
[Dennis Lee Bieber had written:]
>> Or create a protocol where the first 16 bits (in network byte order)
>> contain a length value for the subsequent data, and use a receive
>> process that consists of:
>>
>> leng = ntoh(socket.recv(2))
>> data = socket.receive(leng
> > Well, lets say you have a situation where you're going to be
> > alternating between sending large and small chunks of data. Is the
> > solution to create a NetworkBuffer class and only call send when the
> > buffer is full, always recv(8192)?
>
> Or create a protocol where the first 16
On 2008-03-13, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>> > For example: try creating a local client/server (running on the same
>> > computer) where the server sends the client a fixed amount of data.
>> > Using method A, recv(8192) and sendall( ) with 8192 bytes
>> > worth of data. Do this
On Mar 13, 9:33 am, "Brian Smith" <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > Sent: Wednesday, March 12, 2008 9:47 PM
> > To: [EMAIL PROTECTED]
> > Subject: Socket Performance
>
> > Can anyone explain why socket performance (throughput) varies
> > depending on the amount of data send
[EMAIL PROTECTED] wrote:
> Sent: Wednesday, March 12, 2008 9:47 PM
> To: python-list@python.org
> Subject: Socket Performance
>
> Can anyone explain why socket performance (throughput) varies
> depending on the amount of data send and recv are called with?
>
> For example: try creating a local c
20 matches
Mail list logo