matt, thanks for answering. I can imagine you've got a lot to do and read ...but would you mind reading my first post again?
cron-Archiving ist set up already and working just fine despite the frontend problem. Also I dont think 8000 views is a lot traffic, and I know for a fact that there are not that much unique URLs (50-100 per web I guess). As I said, it worked perfectly fine until last week.
Sure, archiving can use a lot of RAM, but this doesn't seem to be the problem here. It seems that the Smarty engine has some kind of problem (take a closer look at the 2nd code block above). I've never seen an memory error where a process tries to allocate 1,5GB (!) of RAM at once.
cron-Archiving ist set up already and working just fine despite the frontend problem. Also I dont think 8000 views is a lot traffic, and I know for a fact that there are not that much unique URLs (50-100 per web I guess). As I said, it worked perfectly fine until last week.
Sure, archiving can use a lot of RAM, but this doesn't seem to be the problem here. It seems that the Smarty engine has some kind of problem (take a closer look at the 2nd code block above). I've never seen an memory error where a process tries to allocate 1,5GB (!) of RAM at once.