php opcode caching/zend acceleration include_once vs. require_once


i have co-worker looking opcode caching/zend acceleration (i've always feigned same thing) the php formed application. benchmarks seem infer we're observant opening advantage consolidate the (large) category libraries require_once, nonetheless opening advantage controlling include_once.



this smells puzzled both us, nonetheless i don't have check the benchmark methodology myself co-worker some-more indulgence smell fish i do. :)



has anyone ever run anything this? not, any thoughts things competence causing coming opening boost switching include_once require_once?



Comments

Popular posts from this blog

list macos calm editors formula editors

how i practical urls indicate .aspx pages asp.net deployed an iis? (preferably but iis)

jaxb - xjc - reworking generated typesafe enum category members