The flagging table can be slow to access for particularly large datasets.
Create a StorageSchema handler to change the row format of the flagging table and add an index to be equivalent to the following SQL.
ALTER TABLE `flagging` ROW_FORMAT = DYNAMIC
ALTER TABLE `flagging` ADD INDEX `flag_id__uid__session_id` ( `flag_id` , `uid` , `session_id` )Create patch.
None.
None.
None.
We're using the getUserFlagFlagginCount method on the flag.count service. We've got a massive `flagging` table of +300.000 rows and the method is running massively slow. We've been able to fix this by creating a new table index:
ALTER TABLE `flagging` ROW_FORMAT = DYNAMIC
ALTER TABLE `flagging` ADD INDEX `flag_id__uid__session_id` ( `flag_id` , `uid` , `session_id` )This gave us a massive database performance boost. I've not been able to create a patch for this as we speak, though I just made this into a issue for documentation and patching purposes.
Needs work
4.0
Flag core
The patch will have to be re-rolled with new suggestions/changes described in the comments in the issue.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
hetal.solanki → made their first commit to this issue’s fork.
I have reroll #11 patch and after that i have tested it.
It's work for me.
So moving to RTBC.
Thank you!!
Happy to see movement on this issue. Thanks to everyone working on this!