On 7-1-2010 10:51, Reinier van den Born wrote:
The problem occurred when we had a lot of visitors. At some point the source
document was updated and flushed from the cache.
Many requests were coming in and as long as the page wasn't cached each
request resulted in an attempt to regenerate the page.
The result was a load of threads, each of them trying to build the page from
the big document and thus together eating up all memory.
In a way it surprised us that neither Apache httpd's mod_cache or Cocoon's
caching seems to have some mechanism to prevent these redundant parallel
activities.
Question is whether anyone can point us to a solution?
It's not the solution you're asking for, but should prevent your site
going down; limit the number of connections to your backend from apache.
Like so:
ProxyPass / http://somehost:someport/ max=12 smax=6 min=1 ttl=5
See:
http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxypass
Regards,
--
Bartosz Oudekerk
.---------------------------------.-----------------------------------.
| Hippo B.V. | Hippo USA Inc. |
| Oosteinde 11 | 185 H Street, Suite B |
| 1017 WT Amsterdam | Petaluma, CA 94952 |
| The Netherlands | United States of America |
| Tel +31 (0)20 5224466 | +1 (707) 773-4646 |
+---------------------------------+-----------------------------------+
| [email protected] | http://www.onehippo.com |
`---------------------------------^-----------------------------------'
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
Searchable archives can be found at:
MarkMail: http://hippocms-dev.markmail.org
Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
