- that query was altered in 4.2 so that it would not slow down db too much. Now it deletes 100 (or 50?) rows at a time. It's your best bet to fix the problem
- doing it randomly on a statistical basis is the way of php (not just the way of ez)
- you can increase in php.ini gc_probability and lower gc_divisor to have gc happen more frequently. That should make the queries faster if you have a site with lots of traffic (more frequency = fewer rows to delete)
- also diminishing session timeout (3 days by default!) can have a positive impact, as there will be fewer sessions in the db at any given time
- you can set in php.ini gc_probability = 0 and run the query via cronjob, so at least slow queries are not hitting live pages (see the cronjob session_gc.php, added in 4.1)
Principal Consultant International Business
Member of the Community Project Board
You must be logged in to post messages in this topic!
