Re: AppleScript runs slow on Intel Mac's
Re: AppleScript runs slow on Intel Mac's
- Subject: Re: AppleScript runs slow on Intel Mac's
- From: Marc Glasgow <email@hidden>
- Date: Sun, 24 Sep 2006 05:23:24 -0400
In my experiences, one of the biggest overhead issues are certain
brands of scanners which have active (hardware) scan buttons on the
scanner to trigger the scanner (Canon LiDE scanner come to mind, but
present on many scanners). Their background applications poll the
scanner at least once a second for that button-push; add potential
Rosetta overhead and the amount of wasted processing to keep those
buttons on the scanner active can take a really heavy toll (I won't
have hard numbers until my Mac Pro arrives next week).
TIP: If you do most of your scanning within an application that
triggers the scanner (E.G. - Photoshop), disable the button monitor
process for the scanner permanently.
Cheers
=-= Marc Glasgow
Le 23 sept. 2006 à 22:20, Leif Öquist a écrit :
On Sep 23, 2006, at 21:34 EM, Paul Berkowitz wrote:
" I would expect it would have something to do with how many other
processes are running on your Mac, and most especially how much
Free and Inactive RAM you have available."
Without sharing the same level of technical knowledge, I think I
well understood the main lines of Paul Berkowitz posting.
But I still can't understand why Michelle Steiner never comes even
close to the same execution speeds as I and other amateur testers
have achieved with Intel (or other and older) machines? One of the
guys involved reached 1 second with my originally posted test code,
despite simultaneously running a quite power consuming application
(his claim), and that was on a G5. Another guy also run the script
at 1 second on his Intel machine, as have I on an Intel machine.
While Michelle Steiner is never able to run her code faster than 25
seconds on her Intel machine? How can one explain such a huge
difference? Or has it really been explained by the factors refered
to by Paul Berkowitz and Yvan KOENIG?
regards
One more time I repeat that it's Christopher NEBEL which certainly
know well AppleScript which wrote:
Because the first one sends 1500 events to the Finder (which may be
busy doing other things, hence the variance), and the second one
doesn't.
From one machine to an other one, the "other things" may be wasting
different bunches of time.
To get meaningful comparison, the first things to know would be:
how many RAM is installed on the machine
how many space is available on the HD
which HD is installed on each machine (some users replace the
original one by a faster one)
are other processes running on the machines
Before running the test script on my machine, I quitted every othe
app but I didn't check if background processes where running.
Yvan KOENIG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden