note 82293 added to function.session-set-save-handler

When writing your own session handler, particularly database session handlers, play close attention to garbage cleanup and how it could affect server load. To pick a round number example: If you have 1000 requests per minute on session enabled pages, everyone needs a session started but the session garbage cleanup does not need to run every request. Doing so would cause unrequired queries on the database server. In this example, setting your probability/divisor to 1/1000 would be sufficient to clean up old sessions at a minimum once a minute. If you don't need that kind of granularity, increase the gc divisor. Finding the tradeoff between clearing up old sessions and server load is the important aspect here. ---- Server IP: 117.104.160.194 Probable Submitter: 58.6.148.157 ---- Manual Page -- http://www.php.net/manual/en/function.session-set-save-handler.php Edit -- https://master.php.net/note/edit/82293 Del: integrated -- https://master.php.net/note/delete/82293/integrated Del: useless -- https://master.php.net/note/delete/82293/useless Del: bad code -- https://master.php.net/note/delete/82293/bad+code Del: spam -- https://master.php.net/note/delete/82293/spam Del: non-english -- https://master.php.net/note/delete/82293/non-english Del: in docs -- https://master.php.net/note/delete/82293/in+docs Del: other reasons-- https://master.php.net/note/delete/82293 Reject -- https://master.php.net/note/reject/82293 Search -- https://master.php.net/manage/user-notes.php