-
Change Request
-
Resolution: Unresolved
-
Trivial
-
None
-
2.2.4
-
LAMP
From my db log:
UPDATE sessions SET lastaccess=1405069441 WHERE userid=4 AND sessionid='eee0e08926a92d31c0b4b5a7ee4dc948'
UPDATE sessions SET lastaccess=1405069446 WHERE userid=4 AND sessionid='eee0e08926a92d31c0b4b5a7ee4dc948'
UPDATE sessions SET lastaccess=1405069451 WHERE userid=4 AND sessionid='eee0e08926a92d31c0b4b5a7ee4dc948'
UPDATE sessions SET lastaccess=1405069461 WHERE userid=4 AND sessionid='eee0e08926a92d31c0b4b5a7ee4dc948'
UPDATE sessions SET lastaccess=1405069471 WHERE userid=4 AND sessionid='eee0e08926a92d31c0b4b5a7ee4dc948'
UPDATE sessions SET lastaccess=1405069481 WHERE userid=4 AND sessionid='eee0e08926a92d31c0b4b5a7ee4dc948'
UPDATE sessions SET lastaccess=1405069491 WHERE userid=4 AND sessionid='eee0e08926a92d31c0b4b5a7ee4dc948'
UPDATE sessions SET lastaccess=1405069501 WHERE userid=4 AND sessionid='eee0e08926a92d31c0b4b5a7ee4dc948'
I think that updating sessions may be done only if the last update was XXX seconds ago. This should lower the DB usage. XXX could be configurable.