Dariusz Pietrzak wrote:
>
> > I think that it will work.
> Yup, I think I checked that $$data ain't used anywhere else,
> and even if it would be, it'd be enough to nullify it and there
> would still be noticable speed improvement.
>
Thanks much for the optimization Dariusz, and showing me the
> I think that it will work.
Yup, I think I checked that $$data ain't used anywhere else,
and even if it would be, it'd be enough to nullify it and there
would still be noticable speed improvement.
--
Dariusz Pietrzak
Certified Nobody
---
...[snip]...
> > -while($$data =~ s/^(.*?)\<\%(.*?)\%\>//so) {
> > +while($$data =~ /(.*?)\<\%(.*?)\%\>/gso) {
>
> I'm not convinced that this does the right thing. If you don't
> consume the head of the data, then 2nd,3rd,etc ASP block should
> not be picked up correctly. Does a regexp
Dariusz Pietrzak wrote:
>
> Hello,
> I've noticed that parser uses substitute call for parsing,
> changed that and got such results:
>
> New code: 7 wallclock secs ( 7.05 usr + 0.08 sys = 7.13 CPU) @ 14.03/s
> (n=100)
> Old code: 9 wallclock secs ( 8.45 usr + 0.06 sys = 8.51 CPU) @ 11.75/s
Hello,
I've noticed that parser uses substitute call for parsing,
changed that and got such results:
New code: 7 wallclock secs ( 7.05 usr + 0.08 sys = 7.13 CPU) @ 14.03/s
(n=100)
Old code: 9 wallclock secs ( 8.45 usr + 0.06 sys = 8.51 CPU) @ 11.75/s
(n=100)
Diff: -2 wallclock secs (-1.40 u
