At 3:16 PM +0200 4/20/02, Gerald Richter wrote:
>That are really a lot of hits...

Do you ah, Yahoo! :-)

>Did you use any cacheing of the output with Mason and/or Embperl?

Yes for Embperl, but I don't know for Mason.  That was the first time 
I had installed Mason and used it.

>If for
>examples headers or footers are more or less static Mason and Embperl are
>able to cache the generated output, so the Perl code has to be run only
>once. If the header and/or footer is a really static page, then you should
>use the syntax "Text" in Embperl 2,this will speed things up again and
>Embperl 2 use a concept of providers, so it is very simple possible to write
>a pure text provider which will speed up inclusion of static files even
>more, because no Perl code will be involved anymore.

Yes, the pages were static, but we wanted to make sure they were 
evaluated because not all of our included pages are static.  Most of 
them are dynamic as well.

>Another question: Did you use Embperl::Object? Embperl::Object currently
>does some more stat calls then necessary, which slows it down. That is
>something that I like to optimize before the final 2.0 release.

No, I just did a "use Embperl" and set the handler for all .emb2 
pages.  Will this matter one way or the other?

<snip talk about Apache 2.0>

As much as I would love to switch to Apache 2.0, I don't think it 
will gain us much.  We use (or should I say we are stuck with) 
FreeBSD and the thread support is ... well ... not there.  I am sure 
we will be switching to 2.0 eventually, but I don't think it will 
happen any time soon.  We have  some deep modifications in 1.3 right 
now which makes it hard to keep up with that version.

>P.S.S. Do you know what the PHP Accelerator does? Does it some kind of
>output caching? I am not a PHP guru, so I have to ask. If it is some kind of
>caching, maybe we can do a similar thing for Embperl?

Looking at the afterburner code (another PHP Accelerator) all it does 
is copy the internal PHP compile function, and change it with it's 
own.  What the new compile function does it check in the cache to see 
if it is already compile, if so check the timestamp, return the 
cached compiled code or compile it, save it in the cache and return 
it.  It is amazing that at 100+ concurrent connections it doubles the 
request per second compared with no cache.

Brian

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to