This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Slow pipes after upgrade cygwin 1.5.12-1->1.5.13-1 when running boinc
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 3 Mar 2005 12:31:01 -0500
- Subject: Re: Slow pipes after upgrade cygwin 1.5.12-1->1.5.13-1 when running boinc
- References: <1366.130.240.136.220.1109870804.squirrel@130.240.136.220>
- Reply-to: cygwin at cygwin dot com
On Thu, Mar 03, 2005 at 06:26:44PM +0100, Bengt-Arne Fjellner wrote:
>Christopher Faylor skrev:
>> On Thu, Mar 03, 2005 at 05:36:00PM +0100, Bengt-Arne Fjellner wrote:
>>>With boinc running einstein@home at lowest priority ( uses 100% cpu but yields
>>> easily)
>>>simple pipes takes a long time.
>>>Example: from a bash prompt
>>>echo hello|grep -v xyz
>>>with boinc running and 1.5.13-1 takes about 7 seconds. if i stop boinc
>>>it takes parts of a second. after downgrade to 1.5.12-1 with boinc
>>>running: parts of a second.
>>>
>>>i have seen this on two different computers one HT one normal.
>>>
>>>Single commands are still fast.
>>
>> Is there some reason why you'd expect us to know what "boinc" is?
>
>My stupidity i think...
>Really its a community infrastructure for networked computing
>"Berkeley Open Infrastructure for Network Computing"
>http://boinc.berkeley.edu/
>
>With currently this subproject running:
>Einstein@Home
>http://einstein.phys.uwm.edu/
>Dont know if any other subprojects are affected.
If I had to guess, I'd say that boinc is putting itself into a high priority
class for some reason and is eating cpu cycles, causing cygwin's pipe reading
code to stall.
I've made a change to cygwin to put it's pipe reading code into a slightly
higher priority class. This change is in the latest snapshot:
http://cygwin.com/snapshots/
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/