Re: Simple Namespace Proposal

On Sunday 08 July 2007, Stefan Priebsch wrote: > I was asking myself wether loading one large file - possibly from a > cache - might be a lot faster than loading n files. This of course > depends on how expensive disk access is compared to how large your > "binary" gets. That's why I was planning to benchmark it. > > Kind regards, > > Stefan Some incomplete data: I work mostly on Drupal, and in the next version we're splitting up the code base into a lot more smaller files that we can load conditionally. The benchmarks we've done so far indicate that without an opcode cache there's a huge benefit in speed from not loading/parsing code that we're not going to be using (there's a lot of it at this point) as well as a sizable reduction in RAM usage. With an opcode cache the speed difference is negligible, but I believe there's still a RAM savings per-process. More on that when we've completed the process. So it all depends on your caching configuration and use-case. Loading a ton of code that you never use is not good for performance. -- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson