Gist: Snippet to see all PHP include()ed files on your Elgg 2.0 installation
By Steve Clay
Update: this is definitely not worth worrying about. What matters is code loaded, not files.
https://gist.github.com/mrclay/764b8b9d5e61564ec957
Summary: Most pages require ~300 files. Viewing a blog post: 85 engine/classes, 47 engine/lib, 67 views, 47 vendor files
Note: Non-PHP filesystem reads (e.g. images, static view files) are not included.
This post is just informational and I think we have a lot bigger things to focus on than reducing includes, but there's clearly room for improvement in this area.
Feedback and Planning
Discussions about the past, present, and future of Elgg and this community site.
- Evan Winslow@ewinslow
Evan Winslow - 0 likes
- Steve Clay@steve_clay
Steve Clay - 0 likes
- Steve Clay@steve_clay
Steve Clay - 0 likes
You must log in to post replies.Why do we feel like this needs improvement? Is there some reason to believe that 300 includes is going to be expensive after opcode caching is done?
I would not say "need". My thinking was that, as PHP's runtime doubles in speed and we get boot queries down to a very minimum, file access should become a larger share of the remaining overhead.
But the DB will fall over before you get to where that matters.
Not worth thinking about.
More recent anecdote: files don't matter. http://stackoverflow.com/a/29071889/3779