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.

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

Why does the Apc cache still do a lot of resolving? #85

Closed
pietervogelaar opened this issue Apr 6, 2013 · 3 comments
Closed

Why does the Apc cache still do a lot of resolving? #85

pietervogelaar opened this issue Apr 6, 2013 · 3 comments

Comments

@pietervogelaar
Copy link

I have a collection "admin/js/vendor.js" with a lot of vendors combined (jquery, jquery UI, etc). I would like to cache these files in APC because they almost never change. When they does I will clear the APC cache manually.

But when I use xdebug I see that with APC still all the resolving happens. I'm using Vagrant (VM with a shared folder to my host machine) and want to avoid all these slow disk lookups.

Is it possible to check for the path "admin/js/vendor.js" directly in APC and return the content?

@RWOverdijk
Copy link
Owner

That's because it looks up the assets to match against the cache. It's basically just to prevent filtering everytime. So it'd probably be best to use the FilePath cache, as it then never goes through php (and you'll be serving the files directly).

@pietervogelaar
Copy link
Author

Hmm.. okay. Thanks for the explanation and the FilePath tip!

@RWOverdijk
Copy link
Owner

No problem. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants