Deterministic Session GC

Whenever a new request is processed by Odoo, this statement is evaluated: random.random() < 0.001 [1]

1 time out of 1000 in average, it will return True and trigger the Garbage Collection of sessions: sessions that have not been active for more than 1 week will be deleted [2]

This random approach can become a problem in some contexts.

On a highly visited Odoo website, many sessions will be created. Going through all of them will take some time, especially on a slow/loaded FS. The Garbage Collection happening randomly, your users will report you cases of Odoo being randomly slow on random actions. They won’t be able to reproduce these cases and you won’t be able to trace them in your odoo logs neither, because calls’ response time doesn’t include the time Odoo spent on the Garbage Collection.

Moreover, on a heavily loaded server, better be in a position to control when does the Garbage Collection happen. One might want to run it once per night only for example.

That’s why we created this module:

• to disable the default random Garbage Collection

• to enable administrators to replace it by a deterministic approach:

  • either by using the included Scheduled Action;

  • or by calling the added public method ir.autovacuum:gc_sessions() remotely

Table of contents

[options]
(...)
server_wide_modules = web,base_deterministic_session_gc

[options]
(...)
; 1 day = 60*60*24 seconds
session_expiry_delay = 86400

Credits

Authors

• Trobz

Contributors

• Nils Hamerlinck <nils@trobz.com>

Maintainers

This module is maintained by the OCA.

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

This module is part of the OCA/server-tools project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.