Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

cache options #2

Closed
klacke opened this issue Apr 27, 2009 · 1 comment
Closed

cache options #2

klacke opened this issue Apr 27, 2009 · 1 comment
Labels
bug

Comments

@klacke
Copy link
Collaborator

klacke commented Apr 27, 2009

I attempted to turn caching off by specifying "max_num_cached_files = 0" in
yaws.conf, but after the first page access, beam uses 100% CPU, and there
is hundreds of messages like below added to the report.log:

=INFO REPORT==== 3-Aug-2008::21:55:01 ===
Max size cached bytes reached for server "ltop"
@vinoski
Copy link
Collaborator

vinoski commented May 22, 2009

This was caused by attempts to clear the cache and try again, infinitely. I've committed regression tests for this scenario as well as the fix.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@klacke @vinoski