clarify user context cache impact #360
Conversation
|
@lolautruche would you be aware of any useful information about the topic of the HttpCache cache folder cleanup? i wonder how far we should go in here - its some pretty long boxes already, i don't want to digress from FOSHttpCache more in this doc :-) |
|
@dbu Well, the only viable solution for me would be to set up a cronjob purging the cache files... |
|
I have some ideas here @dbu. I think I can implement a decent on-a-regular-basis-cleanup-mechanism in the |
|
A first version is implemented in #373. |
|
@dbu Is this ready to merge? |
|
actually yes. can you check if the wording is understandable and merge/ask me for clarifications? @Toflar did you in the end add something to the taggable store about cleaning up that we should mention in this doc? (guess we merge as is, and you can then do a separate pull request if there is anything to add) |
|
https://github.com/Toflar/psr6-symfony-http-cache-store#pruning-expired-cache-entries We just documented how you can configure it. So imho it's all fine here :) |
|
cool. i think that pruning does not help when you always add more variants, but then what we say in the doc here is still true. |
|
Yeah, I consider "always adding more variants" as being "heavy proxy work". And the basic statement of "don't use the SF HttpCache if you have heavy proxy work" is still true, even with the auto-pruning store 😄 |
fix #356
some documentation to at least tell people how it is. unfortunately we can't really fix the issue.