recently_read table gets very large with sites that have primarily anonymous traffic when "Records delete options" is set to "Count based". Despite the notice that "Older records will be removed" there doesn't seem to be a provision for this to happen in the module code.
Add a cron task that deletes old records or maybe the "count based" option to limit the number of records per user/session should be de-coupled from the process that deletes records based on how old they are. Perhaps this should be broken out into two different settings:
"Delete old records" (with the time intervals as a setting or "never") and "Records per user or session" (with the setting being the number of records to limit the user/session to)
This way a record age-limit can be configured independent of the user/session record limit.
Needs review
1.3
Code
HI @nathan573,
this issue has been fixed, please review the patch.
Thanks
Samit K.
Thank you very much samit.310@gmail.com! I've tested this patch out for at least a month now and it's working.
Cheers!