in reply to 5.8 slowed relaitve to 5.6.1 (by PerlIO?)

Did you compile 5.8 with thread support? Don't. Ultimately you may not be able to make it entirely as fast, since the unicode changes have supposedly slowed things down as well.
  • Comment on Re: 5.8 slowed relaitve to 5.6.1 (by PerlIO?)

Replies are listed 'Best First'.
Re: Re: 5.8 slowed relaitve to 5.6.1 (by PerlIO?)
by ronh (Acolyte) on Jun 10, 2003 at 17:45 UTC
    It's active state build 805 which I believe is no threads. Isn't PerlIO responsible for unicode? Isn't there a way to say: don't expect encoding; go fast? If not, why not?
      It's active state build 805 which I believe is no threads.

      I doubt it. Check the output of perl -V.

      Isn't PerlIO responsible for unicode?

      Supporting unicode means changes in every part of perl. Regex, for exmaple.

      Isn't there a way to say: don't expect encoding; go fast? If not, why not?

      Do you have any idea how hard that is to do in a large and complex codebase like perl5? Parallel code paths for every operation? It's just not feasible.

      I'm very worried/intrigued by this (as I work for a company that's developing a data profiling tool with perl and we mainly use ActivePerl). Have you tried upgrading to 806?