Re: A practical benchmark shows speed challenges for Perl 6
[email protected] (yary) Wed, 30 Mar 2016 16:11:04 -0400
| Newsgroups | perl.perl6.language |
|---|---|
| Message-ID | <CAG2CFAZcbWWw7OEYV1dpjugsPQ_fvYn8Z3pDOTzDUC8cLhsP5Q@mail.gmail.com> |
On Wed, Mar 30, 2016 at 3:20 PM, Elizabeth Mattijsen <[email protected]> wrote: > Thanks for your thoughts! > > I’ve implemented $*DEFAULT-READ-ELEMS in https://github.com/rakudo/rakudo/commit/5bd1e . > > Of course, all of this is provisional, and open for debate and bikeshedding. Thanks! And that was fast! Allowing DEFAULT-READ-ELEMS to be set from the environment's a good idea that I hadn't thought of- since it is a machine-dependent performance tweak, letting it be set outside the code is a good idea. I had originally envisioned this as an "option" to "sub open" for fine-grained control as to which IO::Handles got what DEFAULT-READ-ELEMS, but I'm not sure it belongs there. After all it is a performance-related tweak and I'm liking the idea of it being primarily set from the environment; setting it in the code means you're writing something for a particular host, don't need to change the spec to support that. Is there anything similar on the "write" side- output buffering- that could use this treatment? -y