Menu
Community /Pin to ProfileBookmark
@NogDogJun 10.2008 — #include()/require() just call the operating system's disk I/O interface. Depending on the server's physical and software configuration, there is almost certainly some amount of disk caching going on. Therefore, recently/commonly called files are likely to be in that disk cache RAM rather than having to be read from the disk itself. But even if it's not cached, with today's modern disk drives and I/O buses, it's still not going to be a big deal to read a few thousand bytes long file from the disk, and whether it's 1KB or 20KB is going to make a very small difference -- probably negligible in comparison to the network communication time involved in the HTTP requests and data transfers between the server and client.
So to make a long story short, I would not worry about it unless you (a) are noting performance problems and then (b) have performance profiling test results that indicate changing your include file design/usage would make a non-trivial difference. Otherwise, just code things in the way that seems most logical and that will make maintenance of your code as easy as possible.
OOP: large object includes
I have a photo manager class that controls all photo uploads, resizing, deletes, selects, inserts, updates, and removes.
80% of the time, the class is used only for selects from the database.
Is there any kind of drawback in building a class such as this, where as 80% of the only 20% of the class is being used but the class is included 100% of the time?
I guess my question really is, does every time the file gets included, is it stored in the memory, or does the include look into the memory, realize its already there and use it for processing?
Sign in
to post a comment2 Comments(s) ↴
0
@NogDogJun 10.2008 — #So to make a long story short, I would not worry about it unless you (a) are noting performance problems and then (b) have performance profiling test results that indicate changing your include file design/usage would make a non-trivial difference. Otherwise, just code things in the way that seems most logical and that will make maintenance of your code as easy as possible.