[Date Prev][Date Next][Thread Prev][Thread Next] [Search] [Date Index] [Thread Index]

RE: [MacPerl] MacPERL Performace vs. Intel Class systems



I will bet that the CPU yielding is a big part of the answer.
I also wonder if this IO is going through GUSI, and if that
is adding any cost (like an additional buffer copy?).
tim.
-------
From: 	Tim Rand
Subject: 	Re: [MacPerl] MacPERL Performace vs. Intel Class systems

SO... the File System isn't the bottleneck.  Next, it could be the checking for COMMAND-PERIOD, or calls to the system routine that allows multi-tasking.  These can and do take a lot of additional cycles.  Perhaps they could be called less frequently.  How often are they called now?  Every statement?  Perhaps calling them once per second would be sufficient.


***** Want to unsubscribe from this list?
***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch