Re: non-blocking, recv SOMETIMES takes up to 0.3 seconds [like one connect from 100 000]
From: David Schwartz (davids_at_webmaster.com)
Date: 03/05/04
- Next message: Cameron Laird: "stderr handling (was: TCL and Python)"
- Previous message: David Schwartz: "Re: waiting for read() from more than one sockets"
- In reply to: Andrew Arro: "Re: non-blocking, recv SOMETIMES takes up to 0.3 seconds [like one connect from 100 000]"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 5 Mar 2004 10:47:50 -0800
"Andrew Arro" <arro@arro.ru> wrote in message
news:17118df1.0403050731.2f68ab4a@posting.google.com...
> "David Schwartz" <davids@webmaster.com> wrote in message
> news:<c28gte$9r6$1@nntp.webmaster.com>...
>> "Andrew Arro" <arro@arro.ru> wrote in message
>> news:17118df1.0403041357.450f837@posting.google.com...
>>
>> What operating system?
>>
>> DS
>
>
> i am sorry i have forgotten to add that
>
>
> uname -a
> Linux rh 2.4.20-8 #1 Thu Mar 13 17:54:28 EST 2003 i686 i686 i386
> GNU/Linux
> cat /etc/redhat-release
> Red Hat Linux release 9 (Shrike)
Most likely, I think your threads have just exhausted their time slice.
When they enter the kernel, that's an oppurtunity for a task switch.
DS
- Next message: Cameron Laird: "stderr handling (was: TCL and Python)"
- Previous message: David Schwartz: "Re: waiting for read() from more than one sockets"
- In reply to: Andrew Arro: "Re: non-blocking, recv SOMETIMES takes up to 0.3 seconds [like one connect from 100 000]"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
