Would including a 200 line config file on every page load, cause speed issues?
You need to give more info - what format is the file, how is it interpreted, what does the script do... I've just run a script that took 11 hours to run, so clearly it wouldn't matter in the slightest. But at a guess I'd say that if it's a typical spit bits down the web funnel to Mr. Browser at the end you're talking nothing impact wise.
Its a php file ..
holds some basic functions ive created
about 10 constants ..
um, the database connection
my smarty directory paths and librarys ..
custom session handlers ..
and thats about it!
If you need the functions and stuff, then it would make no difference. It's the same as if you'd have it all in one file.
Yup, like he says, that'll be fine. What you can do to improve things is strip all whitespace out of your Smarty install by running them through the command line version of php with the -w option. It's not something you'd notice by watching a page load, but if you run benchmarks you'll see it's worth it if you're crazy for optimising. If you can avoid using a database connection, like you've got a cached page which won't need it then include it conditionally - that really saves some cycles.
