ake.
Either way, the consistent and pervasive conclusion is that time's CPU
consumption results are significantly understated when multiple processes
are involved. It would be nice to have that acknowledged in the
documentation. If not, well, that's why I have a blog.
-Original Message-
F
upported by significant evidence.
FWIW.
-Original Message-
From: Bruce Dawson [mailto:brucedaw...@cygnus-software.com]
Sent: Wednesday, March 20, 2013 7:44 AM
To: 'Linda Walsh'
Cc: 'bug-bash'
Subject: RE: Bug/limitation in 'time' (kernel setings?)...
Not
kernels are behaving quite similarly.
> What documentation would you have updated?
The bash documentation where it mentions the 'time' command, and the 'time'
documentation.
-Original Message-
From: Linda Walsh [mailto:b...@tlinx.org]
Sent: Wednesday, March 20,
te.. you said your loop took 2 seconds on your 3.2GHz sys.
Yes, but that was then my system was running at 1.1 GHz. When my system
ramps up to its full speed then the 1,000 iterations are done in less than a
second. Our systems are quite consistent there.
-Original Message-
From: Linda Wa
s problematic for determining CPU usage. I'm not
sure what its limitations are.
-Original Message-
From: Linda Walsh [mailto:b...@tlinx.org]
Sent: Tuesday, March 19, 2013 9:10 AM
To: Bruce Dawson; bug-bash
Subject: Re: Bug/limitation in 'time' (kernel setings?)...
Bruce Dawson
ailto:b...@tlinx.org]
Sent: Tuesday, March 19, 2013 8:19 AM
To: Bruce Dawson
Cc: 'Pierre Gaston'; bug-bash@gnu.org; b...@packages.debian.org
Subject: Re: Bug/limitation in 'time' (kernel setings?)...
I think you misunderstand...what Pierre is saying -- your process is
scheduled
@gmail.com]
Sent: Tuesday, March 19, 2013 2:00 AM
To: Bruce Dawson
Cc: bug-bash@gnu.org; b...@packages.debian.org
Subject: Re: Bug/limitation in 'time' (kernel setings?)...
On Tue, Mar 19, 2013 at 5:03 AM, Bruce Dawson
wrote:
> I'll give those a try.
>
> BTW, I just posted the
7;time' and the bash 'time' internal command.
-Original Message-
From: Linda Walsh [mailto:b...@tlinx.org]
Sent: Monday, March 18, 2013 7:15 PM
To: Bruce Dawson
Cc: bug-bash@gnu.org; b...@packages.debian.org
Subject: Re: Bug/limitation in 'time' (kernel seting
day, March 17, 2013 8:36 PM
To: Bruce Dawson
Cc: 'Chris Down'; bug-bash@gnu.org; b...@packages.debian.org
Subject: Re: Bug/limitation in 'time'
Bruce Dawson wrote:
> Yep, we've changed our loops to use roughly that syntax. Unfortunately
> a lot of online resources r
propriate to document
this.
Anyway, if the docs can be updated I think that would be great. If not, no
worries.
-Original Message-
From: Pierre Gaston [mailto:pierre.gas...@gmail.com]
Sent: Saturday, March 16, 2013 11:31 PM
To: Bruce Dawson
Cc: bug-bash@gnu.org
Subject: Re: Bug/limitation i
[mailto:ch...@chrisdown.name]
Sent: Saturday, March 16, 2013 6:58 PM
To: Bruce Dawson
Cc: bug-bash@gnu.org; b...@packages.debian.org
Subject: Re: Bug/limitation in 'time'
Hi Bruce,
On 2013-03-16 17:41, Bruce Dawson wrote:
> I think it's important because when I hit this problem (
org
Cc: Chris Down; Bruce Dawson
Subject: Re: Bug/limitation in 'time'
On Sun, 17 Mar 2013, Chris Down wrote:
> Hi Bruce,
>
> On 2013-03-16 17:41, Bruce Dawson wrote:
>> I think it's important because when I hit this problem (using $(expr)
>> for looping in shell
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='$
uname output: Linux Ubuntu1m 3.2.0-35-generic-pae #55-Ubuntu SMP Wed Dec 5
18:04:39
13 matches
Mail list logo
