Session file cleanup and site performance
Permalink
I'm not sure if they are related but we've noticed a significant amount of lag to the point of the server running out of memory since migrating to Concrete 5.7 running the Fundamental theme.
Are there any job files for cleaning up old session files from the /tmp/ folder? I found a thread about it for 5.6.x but nothing for 5.7
Mine is growing exponentially and it's getting to be an issue. I have no idea if it has anything to do with the performance issue I'm running into but either way I don't like have 100+ MB of session files just lingering about.
As for other potential issues I'm not sure why but when I open the page which watching 'htop' on the server filtered to just that sites client/user it brings up 5 to 7 processes just to serve the page to one browser (mine)... Honestly I'm not sure if this is normal or not for 5.7 or if it might have something to do with the theme which was already rather memory intensive to the point that I had to up the PHP allowed memory allocation.
Need to figure this out as our entire web server is going offline and having to be rebooted or it simply crashes the processes and reloads them (sometimes) which is not idea.
Are there any job files for cleaning up old session files from the /tmp/ folder? I found a thread about it for 5.6.x but nothing for 5.7
Mine is growing exponentially and it's getting to be an issue. I have no idea if it has anything to do with the performance issue I'm running into but either way I don't like have 100+ MB of session files just lingering about.
As for other potential issues I'm not sure why but when I open the page which watching 'htop' on the server filtered to just that sites client/user it brings up 5 to 7 processes just to serve the page to one browser (mine)... Honestly I'm not sure if this is normal or not for 5.7 or if it might have something to do with the theme which was already rather memory intensive to the point that I had to up the PHP allowed memory allocation.
Need to figure this out as our entire web server is going offline and having to be rebooted or it simply crashes the processes and reloads them (sometimes) which is not idea.
