DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 4BI2QwwF240366
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org CFD343858410
MIME-Version: 1.0
References: <CANK+sQnM1iLqQpTwUnGHKSyPrOEk0yuwVFjMJ0CURttjOLW8ZA AT mail DOT gmail DOT com>
 <20241212142517 DOT 5718c29573457aad0cbee671 AT nifty DOT ne DOT jp>
 <CANK+sQkBo_XFURtdO+eU+yHqDJw24jKUVzSnxmvAePkjT2PNTQ AT mail DOT gmail DOT com>
 <20241212170927 DOT 94b70a7bccd8926156b005ab AT nifty DOT ne DOT jp>
 <CANK+sQn7AkA4FJAoJy-bFhhdzJ0FwPRS47Le21zqoAWW5=yNhg AT mail DOT gmail DOT com>
 <20241212215357 DOT 9816faca5514fe0145bc16f3 AT nifty DOT ne DOT jp>
 <CANK+sQkRTqijOo_16cFknRsK5kf=zaR3-pYsxc6L4wjoDmL1gg AT mail DOT gmail DOT com>
 <20241212225631 DOT 6e940a2caeba079577a2539e AT nifty DOT ne DOT jp>
 <CANK+sQ=toRmSrLKTwEe7h3YZPf9-HG_WVPf2-2mC1zJZg57EbA AT mail DOT gmail DOT com>
In-Reply-To: <CANK+sQ=toRmSrLKTwEe7h3YZPf9-HG_WVPf2-2mC1zJZg57EbA@mail.gmail.com>
Date: Wed, 18 Dec 2024 10:25:25 +0800
Message-ID: <CANK+sQnf5uRexwgNo3PSCGQEyuS93YMgSpUJC3xwb9Kkp9N68g@mail.gmail.com>
Subject: Re: procps can work
To: Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
Cc: cygwin AT cygwin DOT com
From: =?utf-8?b?5Yev5aSPIHZpYSBDeWd3aW4=?= <cygwin AT cygwin DOT com>
Reply-To: =?UTF-8?B?5Yev5aSP?= <walkerxk AT gmail DOT com>
Content-Type: text/plain; charset="utf-8"
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>
Content-Transfer-Encoding: 8bit

So, there is a big performance difference between windows and linux?
On linux, 3000 processes just take about 0.1 second.

On Fri, Dec 13, 2024 at 10:22 AM 凯夏 <walkerxk AT gmail DOT com> wrote:

> After I upgraded to 3.6.0-0.287.g1d1451ccd2a6, procps can work now.
> It doesn't just hang for a short time, I have a crontab job to log process
> information into file every minute, and I found ps running for hours, so I
> have to stop the job.
>
> On Thu, Dec 12, 2024 at 9:56 PM Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
> wrote:
>
>> On Thu, 12 Dec 2024 21:48:05 +0800
>> 凯夏 wrote:
>> > 31 AT 21:47:19#xiakai1 AT tp/~> /usr/bin/ps|wc -l
>> > 146
>> > 31 AT 21:47:21#xiakai1 AT tp/~>
>> >  about 146 processes
>>
>> It is possibly just due to too many processes for procps, isn't it?
>> I tested procps with 200 processes (sleep 100) and it took about
>> 10 seconds.
>>
>> What kind of CPU does your machine have?
>>
>> --
>> Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
>>
>

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple