So would you think the CPU consumption and resources of 1 reload per minute for millions of vhosts in the database would be less than just using a pool of database connections to do a lookup on top of a HTTP request? Because what if you only have a couple of hundred frequently accessed hosts, they'd have to wait for the others to be reloaded, but if you had some sort of caching and had it justby nick - Ideas and Feature Requests
Are you referring to 1 reload per minute?by nick - Ideas and Feature Requests
Okay, a large number. ;-) I wasn't really meaning to put any numerics to it initially, but in your opinion how many database request would you estimate would be done?by nick - Ideas and Feature Requests
Well, a few hundred? thousands? :-\ I'm just trying to stir up debate here to see what would be the best direction for a module like this. Perhaps Neil has more of an idea of how large his database would be for him. I'm just wondering if a select statement per HTTP request is better than a refresh every 10 mins or so, particularly for large systems?by nick - Ideas and Feature Requests
That's quite interesting having it refresh. Would that put much of a strain on the running of things? Particular for ISPs like the one Neil is representing with large numbers of vhosts? Or would having a module which queries the database when a HTTP request is made be more efficient? Maybe it would depend on the type of setup you've got going. I mean, for servers holding many hosts with not mucby nick - Ideas and Feature Requests
I've been looking for something like this for months now, and I don't think there is a module which does this - meaning I was looking into creating something like this too, alas I've not found much time yet. I've noticed some solutions/work arounds in apache and lighttpd rebuild the vhost files on a restart, or require a restart when a new host is added to the database. It'd be interesting to pby nick - Ideas and Feature Requests