analyse this linux file sharing related question 3517

siliconmike

Not from me.. I have similar situations, but I just always generate on demand. I've thought about schemes like what you propose, but it didn't seem worth the trouble for me; my site is only handling a little more than half a million pages a month; so that's only 12 ppm on average so if the cpu can't handle that.. but then again it would mean that some people would get faster results, so I have toyed with it now and then.

If the load is big and the regen is cpu intensive, this would certainly improve performance. I guess you could do it by always doing some scripting too : the page never really exists but the script has its own cache and reads from that until it is considered stale, then takes the time to regen it. Small cpu load most of the time, big sometimes.

Or set a lockfile in your method so you don't write it more than once.. slight delay for a few users and when the lock is clear they go read the static file rather than continuing with the regen? Little more work, but might be worth it.

-- Tony Lawrence