You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whimsical.apache.org by Sam Ruby <ru...@intertwingly.net> on 2017/12/23 15:33:26 UTC
roster performance
It now takes over 30 seconds to load
https://whimsy.apache.org/roster/committee/incubator; and nearly 30
seconds to load
https://whimsy.apache.org/roster/committee/incubator.json
Any ideas on why this might be? Perhaps the cross-check isn't scaling
linearly with the number of IPMC members? Perhaps this page should be
split into multiple pages (either across the board, or just for PMCs
above a certain size). Perhaps the page should be loaded
incrementally, with more information being shown as it becomes
available? Perhaps data should be cached on the client and shown
immediately and updated when information is sent from the server?
- Sam Ruby
Re: roster performance
Posted by sebb <se...@gmail.com>.
On 23 December 2017 at 16:42, sebb <se...@gmail.com> wrote:
> On 23 December 2017 at 15:33, Sam Ruby <ru...@intertwingly.net> wrote:
>> It now takes over 30 seconds to load
>> https://whimsy.apache.org/roster/committee/incubator
>
> Takes under 10s logged in as testsebb, around 40 as sebb.
>
>> ; and nearly 30
>> seconds to load
>> https://whimsy.apache.org/roster/committee/incubator.json
>
> Takes under 2 seconds logged in as testsebb, around 30 as sebb.
>
> Both the above with Chrome (with debug, cache disabled) logged on as testsebb.
>
>> Any ideas on why this might be?
>
> Looks like the additional information extracted/processed for logins
> with karma is taking a long time.
However further testing shows that subsequent requests take less time.
It looks like there is some caching happening on the server (or
perhaps there is a caching proxy?)
>> Perhaps the cross-check isn't scaling
>> linearly with the number of IPMC members? Perhaps this page should be
>> split into multiple pages (either across the board, or just for PMCs
>> above a certain size). Perhaps the page should be loaded
>> incrementally, with more information being shown as it becomes
>> available? Perhaps data should be cached on the client and shown
>> immediately and updated when information is sent from the server?
>>
>> - Sam Ruby
Re: roster performance
Posted by sebb <se...@gmail.com>.
On 23 December 2017 at 15:33, Sam Ruby <ru...@intertwingly.net> wrote:
> It now takes over 30 seconds to load
> https://whimsy.apache.org/roster/committee/incubator
Takes under 10s logged in as testsebb, around 40 as sebb.
> ; and nearly 30
> seconds to load
> https://whimsy.apache.org/roster/committee/incubator.json
Takes under 2 seconds logged in as testsebb, around 30 as sebb.
Both the above with Chrome (with debug, cache disabled) logged on as testsebb.
> Any ideas on why this might be?
Looks like the additional information extracted/processed for logins
with karma is taking a long time.
> Perhaps the cross-check isn't scaling
> linearly with the number of IPMC members? Perhaps this page should be
> split into multiple pages (either across the board, or just for PMCs
> above a certain size). Perhaps the page should be loaded
> incrementally, with more information being shown as it becomes
> available? Perhaps data should be cached on the client and shown
> immediately and updated when information is sent from the server?
>
> - Sam Ruby