f



8 second delays on Mac OS X 10.3.4 on 1.6 GHz G5 with 1GB ram, 2 * 80 GByte drives

I posted this back in Feb on comp.sys.mac.misc and got several
answers, but I still haven't found the source of the problem or the
fix. I don't see any disk/cpu activity at the delay times, and all the
sleep functions are off.

The previous thread can be found by google groups search: "mac os x 8
seconds delay".  Here is what I wrote before:

> I am wondering if other Mac owners are having this problem:
> 
> I open a terminal window. I enter ls -l to look at the files in my home 
> directory (or any other directory).  I notice that if 5 minutes (or so) 
> elapse before doing the ls -l command, there is a 8 second or so pause 
> before the listing starts.  If I repeat the command, there is no delay.
> 
> It is like the energy saver is set "Put the hard disk(s0 to sleep when 
> possible", but it is not selected, and all the sleep options are "never".
> 
> This is on a G5, 1.6 GHz, OS X (10.3.2), 1 GByte RAM two 80 GByte 
> drives, etc.
> 
> I am trying very hard to enjoy switching to OS X from linux and solaris 
> (before that, MS Windows), but this kind of response is discouraging.
> 
> This is just the most obvious way to see the delay.  I think it also 
> shows up when opening another window or application at times.
> 
> Boyd
> 
> 

Here are the interesting results from a perl script that runs the 
command: 'ls -l /tmp/* > /dev/null' every 10 seconds.  If there is a 
delay I get a message telling how long the delay was and when it 
occurred.  Otherwise I just get a counter:

1 2 3 4 5 6 7 8 9 10 11 12
  THAT WAS A LONG ONE - it delayed 8 seconds
  Happened at Tue Feb 24 17:08:54 2004
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
27
28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
51
52 53 54 55 56 57 58 59 60
  THAT WAS A LONG ONE - it delayed 8 seconds
  Happened at Tue Feb 24 17:19:05 2004
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
27
28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
51
52 53 54 55 56 57 58 59 60 61
  THAT WAS A LONG ONE - it delayed 8 seconds
  Happened at Tue Feb 24 17:29:25 2004
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
27
28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
51
52 53 54 55 56 57 58 59 60 61
  THAT WAS A LONG ONE - it delayed 8 seconds
  Happened at Tue Feb 24 17:39:45 2004
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
27
28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
51
52 53 54 55 56 57 58 59 60 61 62
  THAT WAS A LONG ONE - it delayed 8 seconds
  Happened at Tue Feb 24 17:50:15 2004
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
27
28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50
51
52 53 54 55 56 57 58 59 60 61
  THAT WAS A LONG ONE - it delayed 8 seconds
  Happened at Tue Feb 24 18:00:35 2004

Any ideas?  Maybe it is the update (sync) command doing it, but that
is
supposedly every 30 seconds.

Boyd
0
tbmoore (8)
6/24/2004 2:37:13 PM
comp.sys.mac.hardware.misc 4192 articles. 1 followers. Post Follow

3 Replies
386 Views

Similar Articles

[PageSpeed] 3

On 24/06/2004 10:37 AM, Boyd Moore wrote:

>>I am wondering if other Mac owners are having this problem:
>>
>>I open a terminal window. I enter ls -l to look at the files in my home 
>>directory (or any other directory).  I notice that if 5 minutes (or so) 
>>elapse before doing the ls -l command, there is a 8 second or so pause 
>>before the listing starts.  If I repeat the command, there is no delay.
>>
>>It is like the energy saver is set "Put the hard disk(s0 to sleep when 
>>possible", but it is not selected, and all the sleep options are "never".
>>
>>This is on a G5, 1.6 GHz, OS X (10.3.2), 1 GByte RAM two 80 GByte 
>>drives, etc.
>>
>>I am trying very hard to enjoy switching to OS X from linux and solaris 
>>(before that, MS Windows), but this kind of response is discouraging.
>>
>>This is just the most obvious way to see the delay.  I think it also 
>>shows up when opening another window or application at times.
>>
Which ls are you using?  Does any of these times correspond with 
anything interesting in the system.log?  I know that the Fink ls 
complains about not being prebound constantly, but I've never seen it 
cause this kind of problem on several boxes.

Weird one.  Sorry I can't help further.
0
clvrmnky
6/24/2004 5:07:10 PM
In article <220f0087.0406240637.66089a23@posting.google.com>,
 tbmoore@bealenet.com (Boyd Moore) wrote:
> > 
> > I open a terminal window. I enter ls -l to look at the files in my home 
> > directory (or any other directory).  I notice that if 5 minutes (or so) 
> > elapse before doing the ls -l command, there is a 8 second or so pause 
> > before the listing starts.  If I repeat the command, there is no delay.
> > 
.....
> 
> Any ideas?  Maybe it is the update (sync) command doing it, but that
> is
> supposedly every 30 seconds.

where is your "Home" directory?
if there are any network paths involved in that, 
or any network volumes mounted, then lookupd may get
involved, and if any routes in your routing table(s)
expire at 10 minutes (not unreasonable) there may be at
least an arp, possibly a DNS lookup ...

just my 2c.
0
J
6/25/2004 2:11:48 AM
"J.Random Luser" <user@host.domain> wrote in message news:<user-D3CB13.14114825062004@scream.auckland.ac.nz>...
> In article <220f0087.0406240637.66089a23@posting.google.com>,
>  tbmoore@bealenet.com (Boyd Moore) wrote:
> > > 
> > > I open a terminal window. I enter ls -l to look at the files in my home 
> > > directory (or any other directory).  I notice that if 5 minutes (or so) 
> > > elapse before doing the ls -l command, there is a 8 second or so pause 
> > > before the listing starts.  If I repeat the command, there is no delay.
> > > 
>  ....
> > 
> > Any ideas?  Maybe it is the update (sync) command doing it, but that
> > is
> > supposedly every 30 seconds.
> 
> where is your "Home" directory?
> if there are any network paths involved in that, 
> or any network volumes mounted, then lookupd may get
> involved, and if any routes in your routing table(s)
> expire at 10 minutes (not unreasonable) there may be at
> least an arp, possibly a DNS lookup ...
> 
> just my 2c.

My home directory is /Users/boyd, the standard place, and the ls I am
using is the standard /bin/ls.  When I studied this a while back, I
watched to see if lookupd was particularly active at the delay times,
and it wasn't.  But, on the other hand, it may be waiting on a
timeout.  I will check in that direction next.  Thanks.

Boyd
0
tbmoore
6/25/2004 9:38:10 AM
Reply: