One of the most important modules, and one that is very frequently used in development involving Drupal, is controlling the expiry of rows from the session table older than a certain time. On busy sites, the sessions table can grow to be very large, and that can cause slow accesses to it, as well as slow writes due to locking, leading to performance bottlenecks.
By trimming the table regularly, the above bottlenecks are avoided.
Drupal uses the PHP garbage collection mechanism to clean up the sessions table, but this mechanism depends on PHP’s configuration, and can fire for any session.
This module moves this functionality to cron, and hence is a background process, and is consistent and predictable regardless of PHP’s garbage collection configuration.
Click here to read the full story.
Sitecore Certification for Second Batch of WS Digital ExpertsNovember 12th, 2015
WS CMS Partners are All Leaders in Gartner's Magic Quadrant 2015August 20th, 2015
Open Source vs Proprietary Platforms: What Works for Government2Citizen (G2C) PortalsMarch 16th, 2015
Ektron + EPiServer - What Does the Merger Mean for Customers?February 17th, 2015
3 Reasons Why You Should Consider Upgrading to Ektron 9 Right Now!July 5th, 2013
Ektron 8.7 Brings Support For Cloud Computing, SharePoint And An Improved Editor To Make Your Life EasierMay 3rd, 2013