Re: [PATCH 01/11] Improve patch listing performance (~3x)

2018-09-10 Thread Stephen Finucane
On Mon, 2018-09-10 at 23:26 +1000, Daniel Axtens wrote: > Stephen Finucane writes: > > > On Fri, 2018-08-10 at 18:00 +1000, Stewart Smith wrote: > > > There's two main bits that are really expensive when composing the list > > > of patches for a project: the query getting the list, and the query

Re: [PATCH 01/11] Improve patch listing performance (~3x)

2018-09-10 Thread Daniel Axtens
Stephen Finucane writes: > On Fri, 2018-08-10 at 18:00 +1000, Stewart Smith wrote: >> There's two main bits that are really expensive when composing the list >> of patches for a project: the query getting the list, and the query >> finding the series for each patch. >> >> If we look at the

Re: [PATCH 01/11] Improve patch listing performance (~3x)

2018-09-09 Thread Stewart Smith
Stephen Finucane writes: > On Fri, 2018-08-10 at 18:00 +1000, Stewart Smith wrote: >> There's two main bits that are really expensive when composing the list >> of patches for a project: the query getting the list, and the query >> finding the series for each patch. >> >> If we look at the query

Re: [PATCH 01/11] Improve patch listing performance (~3x)

2018-08-31 Thread Stephen Finucane
On Fri, 2018-08-10 at 18:00 +1000, Stewart Smith wrote: > There's two main bits that are really expensive when composing the list > of patches for a project: the query getting the list, and the query > finding the series for each patch. > > If we look at the query getting the list, it gets a lot

Re: [PATCH 01/11] Improve patch listing performance (~3x)

2018-08-30 Thread Daniel Axtens
Stephen Finucane writes: > On Sat, 2018-08-11 at 04:28 +1000, Daniel Axtens wrote: >> Stewart Smith writes: >> >> > There's two main bits that are really expensive when composing the list >> > of patches for a project: the query getting the list, and the query >> > finding the series for each

Re: [PATCH 01/11] Improve patch listing performance (~3x)

2018-08-29 Thread Stewart Smith
Stephen Finucane writes: > On Sat, 2018-08-11 at 04:28 +1000, Daniel Axtens wrote: >> Stewart Smith writes: >> So, further to our conversation with Konstantin, I tested this against >> Django 2.0. It still saves us some time - it means we no longer load the >> following fields: >> >>

Re: [PATCH 01/11] Improve patch listing performance (~3x)

2018-08-29 Thread Stephen Finucane
On Sat, 2018-08-11 at 04:28 +1000, Daniel Axtens wrote: > Stewart Smith writes: > > > There's two main bits that are really expensive when composing the list > > of patches for a project: the query getting the list, and the query > > finding the series for each patch. > > > > If we look at the

Re: [PATCH 01/11] Improve patch listing performance (~3x)

2018-08-12 Thread Stewart Smith
Daniel Axtens writes: > Stewart Smith writes: > >> There's two main bits that are really expensive when composing the list >> of patches for a project: the query getting the list, and the query >> finding the series for each patch. >> >> If we look at the query getting the list, it gets a lot of

Re: [PATCH 01/11] Improve patch listing performance (~3x)

2018-08-10 Thread Daniel Axtens
Stewart Smith writes: > There's two main bits that are really expensive when composing the list > of patches for a project: the query getting the list, and the query > finding the series for each patch. > > If we look at the query getting the list, it gets a lot of unnesseccary > fields such as

[PATCH 01/11] Improve patch listing performance (~3x)

2018-08-10 Thread Stewart Smith
There's two main bits that are really expensive when composing the list of patches for a project: the query getting the list, and the query finding the series for each patch. If we look at the query getting the list, it gets a lot of unnesseccary fields such as 'headers' and 'content', even