cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Berin Loritsch <>
Subject Re: map:read performance penalty
Date Wed, 17 Oct 2001 17:57:47 GMT
Luca Morandini wrote:
> Folks,
>         I'd like to know whether the use of <map:read> sitemap component has any
> significant impact on performance.
>         My traditional approach is to have all static content mapped directly to
> the web-server. For instance all my images (JPG, GIF, ...) are in the
> /graphics directory, thus avoiding the need to go through Tomcat/Cocoon
> (/graphics is a top-level virual directory).
>         While this is faster, I'd like to know whether using <map:read> to serve
> those resources (a more flexible approach indeed) has a serious impact on
> performance.
>         One last thing, my images tend to be large (100KB or so).

I have not noticed a big difference in performance.  The Readers currently included
with Cocoon do not load the whole resource into memory before serializing, so it
won't have any greater impact on system scalability if your images were 100MB or so.
The buffer size is between 1k and 8k per concurrent reader--so it isn't as big a
concern otherwise.

The caveat to the above statement is caching.  Cocoon does cache if it can, there is
a configurable threshold so that cacheable items taking up more than X bytes will not
be cached.

Seriously, I have run 200 threads attacking my machine, and readers are surprisingly
well behaved.

Please check that your question has not already been answered in the
FAQ before posting. <>

To unsubscribe, e-mail: <>
For additional commands, e-mail: <>

View raw message