[PATCH v2 2/3] models: Split Patch into two models

Finucane, Stephen stephen.finucane at intel.com
Wed Mar 16 02:22:17 AEDT 2016

On 13 Mar 22:55, Stephen Finucane wrote:


> This comes at the cost of an additional JOIN per item on the main
> screen, but this seems a small price to pay for the additional
> functionality gained. To minimise this, however, caching will be added.


So now that we have django-debug-toolbar working, I was able to inspect
the actual database queries to see how the INNER JOIN affected
performance. The end result: virtually no difference. This is great
news, as we get the benefits that this change brings with virtually no
downsides. We can still add some caching, but this will give us an
improvement on existing performance.


More information about the Patchwork mailing list