At 10:04 AM -0500 6/4/97, Randy Bradley wrote: >>You all have correctly identified file system performance as the bottleneck. >> > > I guess all of you cannot be wrong. However, I'm not so easy to >convince. I do think that the file system on Mac is geared toward >binary/block IO and can suffer greatly doing text IO, depending on the >compiler/intrepreter. I have not looked at the source of MacPERL an I know >many of you are intimate with the source. If you say it cannot go faster, >I'm sure that is the case ;-) > > However, consider the following code: Good, you did what I had wanted to do, but don't have a C compiler. This PERL script that I posted was originally written from a C program that was almost identical to the one you posted. 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. Also I noticed that $| is defaulted to ON (1) on my 68K machine. I tried turning it to 0 with no change in performance. Could it be that this is hard-coded in MacPERL? I doubt it. ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch