Roundup Tracker - Issues

Issue 2550532

classification
caching tracker instance objects across requests.
Type: resource usage Severity: normal
Components: Web interface Versions: devel
process
Status: closed accepted
:
: stefan : richard, stefan
Priority: :

Created on 2009-03-20 16:55 by stefan, last changed 2010-02-23 03:26 by richard.

Messages
msg3666 Author: [hidden] (stefan) Date: 2009-03-20 16:55
Each time a roundup tracker instance object is created, it needs to do a
lot of work: establish database connection, load (and process) TAL page
templates, etc.
At present, only the roundup_server frontend caches instance objects to
avoid this overhead. While adding something equivalent to the mod_python
interface (apache.py) is straight forward, I wonder about the implications.
How thread-safe is Roundup ? (In particular, the RDBMS cache handling. ?)
Is it safe to simply turn on caching in apache.py, even in the face of
requests coming in from multiple apache threads in parallel ?

Richard, while I would like to work on this, I'm afraid I lack some
fundamental understanding in order to do this efficietly. Could you
please help me clarify this ?

Thanks,
        Stefan
msg4031 Author: [hidden] (richard) Date: 2010-02-23 03:26
As far as I can tell this was implemented in r4317
History
Date User Action Args
2010-02-23 03:26:27richardsetstatus: new -> closed
resolution: accepted
messages: + msg4031
2009-03-20 16:55:08stefancreate