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? In database design you should almost never have perfect normalization due to performance issues. I know this point will be ignored, but it’s at least worth mentioning. 

On Mon, Jun 3, 2019 at 4:44 PM Chico Venancio <chicocvenancio@gmail.com> wrote:
Hey John, 
What is the specific normalization you believe is unneeded? 


Chico Venancio

Em seg, 3 de jun de 2019 16:58, John <phoenixoverride@gmail.com> escreveu:
This is a prime example of over normalization. We are normalizing and making things slower.

On Mon, Jun 3, 2019 at 3:38 PM Jesse Plamondon-Willard <pathoschild@gmail.com> wrote:
Sure! I just fetch the comment ID in the original query ([1]), and fetch the comment text with a separate query ([2]). You need n+1 queries based on the number of records, but the performance is adequate for my use cases.


On Mon, 3 Jun 2019 at 14:51, Huji Lee <huji.huji@gmail.com> wrote:
Out of curiosity, Jesse, can you share the query after that change, so it is all stored in this thread for future reference?
_______________________________________________
Wikimedia Cloud Services mailing list
Cloud@lists.wikimedia.org (formerly labs-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud
_______________________________________________
Wikimedia Cloud Services mailing list
Cloud@lists.wikimedia.org (formerly labs-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud
_______________________________________________
Wikimedia Cloud Services mailing list
Cloud@lists.wikimedia.org (formerly labs-l@lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud