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

[D.Thomas@vthrc.uq.edu.au (Danny Thomas)]

"Paul J. Schinder" <schinder@pjstoaster.pg.md.us> writes
>One single benchmark means nothing
yup - benchmarks are only useful insofar as they approximate the sort of
work you'll be running.

>In 6 or so months, we can all upgrade what machines we can to Rhapsody and
>lose the file system bottleneck.  Until then, there's little to be done.

indeed.

Even the post MacOS 8 release with the new filesystem (HFS+) won't be
running it native. One assumes there's good technical reasons for this
which hopefully will be addressed in the next major release of MacOS.

to drift further off the topic of this list, I seem to remember reading
that Frontier was going to be ported to Rhapsody (being an app it's easier
than AppleScript) but I'd like to see Rhapsody include Perl as one of the
standard scripting languages. I think Matthias said that the two big
problems using MacPerl as a scripting language are:
  1) it's use of memory
  2) single-threaded nature

I'm guessing that by the time of the unified Rhapsody release in a year or
so, that perl will include multi-threading (slated for perl 5.006).

Danny Thomas



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