Re: [Cloud] Toolforge SQL performance issue with new comment table

2019-06-04 Thread Jaime Crespo
I think there is a misunderstanding that normalization reduces performance (even for analytic queries)- all the opposite, due to a lower amount of actual data stored, the memory to disk ratio increases and while joins may increase cpu usage, the usage, even on labs, is normally negligible. In parti

Re: [Cloud] Toolforge SQL performance issue with new comment table

2019-06-04 Thread Jaime Crespo
There is another factor that contributes both to the thinking of too much normalization and performance issues: There is now multiple "*_temp" tables that are required to join things like comment and revision, or actor and revision. These tables are temporary and only necessary during the migratio

Re: [Cloud] Toolforge SQL performance issue with new comment table

2019-06-04 Thread Daniel Kinzler
Am 03.06.19 um 22:50 schrieb John: > With the introduction of the actor and comment tables, I have seen a notable > spike in query times. Take a look at Jessie’s query. A query that used to > take a > couple of seconds now takes almost 5 minutes. It also spanned what 8-9 > different > joins now?

Re: [Cloud] [Cloud-announce] Dropping user text columns from replica views 2019-05-27 now 2019-06-03

2019-06-04 Thread Brooke Storm
The work on this is completed across the replicas. We’ve created a wikitech page to describe the change further and help share solutions to problems caused by the changes https://wikitech.wikimedia.org/wiki/News/Actor_storage_changes_on_the_Wiki_Replicas

[Cloud] Another SQL optimization request

2019-06-04 Thread Huji Lee
Hi all, I have a query that used to do a GROUP BY on rev_user and now I have migrated it to do so using rev_actor instead. The latest version looks like this and its performance is not good

Re: [Cloud] Another SQL optimization request

2019-06-04 Thread Bryan Davis
On Tue, Jun 4, 2019 at 4:54 PM Huji Lee wrote: > > Hi all, > > I have a query that used to do a GROUP BY on rev_user and now I have migrated > it to do so using rev_actor instead. The latest version looks like this [0] > and its performance is not good [1] at all. In fact, I left it running for

Re: [Cloud] Another SQL optimization request

2019-06-04 Thread Huji Lee
All great answers; thank you! Let's wait and see what comes out of T224850. On Tue, Jun 4, 2019 at 8:21 PM Bryan Davis wrote: > On Tue, Jun 4, 2019 at 4:54 PM Huji Lee wrote: > > > > Hi all, > > > > I have a query that used to do a GROUP BY on rev_user and now I have > migrated it to do so usin