Roundup Tracker - Issues

Message7597

Author rouilj
Recipients marcus.priesch, mbehrle, rouilj, schlatterbeck
Date 2022-07-01.11:21:41
Message-id <20220701112140.B63BF6A01A6@pe15.cs.umb.edu>
In-reply-to <20220701081837.wrp2izp3rmo7h2kn@runtux.com>
In message <20220701081837.wrp2izp3rmo7h2kn@runtux.com>,
Ralf Schlatterbeck writes:
>
>
>Ralf Schlatterbeck added the comment:
>
>On Tue, Jun 28, 2022 at 01:54:03AM +0000, John Rouillard wrote:
>> 
>> I am attaching a new patch. Marcus can you apply this and verify that
>> using the feature flag as documented enables the same speedup you
>> reported with your tests.
>
>John, I've just looked at your patch and it seems to require that the
>user changes some things in the guts of roundup?
>What do you think about making this a config option that for now is off
>by default and will later becom on by default (next release)? We can
>warn in the release notes that people should test the option and that it
>boosts performance (especially if there are many detectors and/or
>templates).

Npe the only things that should change to enable it is the wsgi.py
wrapper written by the user or retreived from the frontends directory.

No internal code changes need to be done by the user to enable it. At
the point where the patch's action has to happen in
roundup/cgi/wsgi_hander.py there no tracker is open, so no way to read
the config file.
History
Date User Action Args
2022-07-01 11:21:41rouiljsetrecipients: + rouilj, schlatterbeck, mbehrle, marcus.priesch
2022-07-01 11:21:41rouiljlinkissue2551212 messages
2022-07-01 11:21:41rouiljcreate