3 ms·
> it will just pull it from the cache, not needing to be parsed or read from disk. I don't believe PHP's ini_read caches anything. Sure, your OS cache is going
by russss 16y ago
> it will just pull it from the cache, not needing to be parsed or read from disk.
I don't believe PHP's ini_read caches anything. Sure, your OS cache is going to have that file in, but PHP still has to do the fopen(), fread(), parse, fclose() dance on every page hit. This does not happen with an opcode-cached source file.
I have actually benchmarked this. Amortized across billions of page hits per month it produces a notable saving.
Kudos points out that you could use APC - this is absolutely true but IMO it basically equates to doing the same thing in a more complex way.
> Configuration stored in a PHP file is bad. Changing working code simply because you want to add a new slave is a horrible idea. It would be like having to recompile Apache from source every time you want to add a new vhost because all the entries are written in C.
This is a false comparison between interpreted and compiled languages. Not to mention that plenty of C programs use #defines for configuration. Varnish even translates its configuration language into C and dynamically loads it as a module, which provides significant flexibility.
In a dynamic language, and where you trust the person doing the configuration, there's no reason why your configuration shouldn't be in a source file. Both Django and Rails do it this way.
- user24 16y ago> I don't believe PHP's ini_read caches anything. so check if the ini file key is in memcache, if so get it from there, if not, ini_read it and populate the cache. Not hard.
- carbon8 16y ago"In a dynamic language, and where you trust the person doing the configuration, there's no reason why your configuration shouldn't be in a source file. Both Django and Rails do it this way." Not true. In Rails, sensitive information like database passwords or AWS keys are not stored in the source, you store them in configuration files, YAML files by default. It's also widely recommended that these not be checked into version control.
- russss 16y agoMy bad - it's been a while since I touched Rails and my memory was rusty.
- jasonlotito 16y ago> I don't believe PHP's ini_read caches anything. I wasn't referring to straight PHP. There are multiple ways to cache the config file's contents so you don't have to hit the disk to read. > This is a false comparison between interpreted and compiled languages. Not to mention that plenty of C programs use #defines for configuration. Your misunderstanding me here. I'm not saying #defines are bad. However, they are a different level of configuration from vhosts. You aren't #defining your virtual hosts. Same with php. You have the C code with specific options being set, and then php.ini for the user facing stuff. > In a dynamic language, and where you trust the person doing the configuration, there's no reason why your configuration shouldn't be in a source file. Except we saw at least one reason today.