- Issue created by @adriancotter
- 🇺🇸United States adriancotter
In looking further this definitely related to 3399969. So am going to make some comments in that thread.
- Status changed to Closed: duplicate
10 months ago 7:31am 8 February 2024
After upgrading to Group 2.x last night, our site started to lag, and really struggled as traffic took off during the day. In our blackfire monitor there is an obvious uptick after I pushed the code that only grew throughout the day as traffic increased.
It seems like a bigger memory footprint
We are still on 9.5.11
We do use other group modules. Group Taxonomy and Group Content Menu.
We've a number of patches (particularly one to make group taxonomy work with 2.0).
We're not on 2.2.2 because of a bug with a token patch (or so it seems).
In digging in through Blackfire page profiles, we were notified of high SQL query numbers. Comparing some numbers of profiles of pages firing on 2.x and 1.x, the 2.x code seems to be firing many more times. And consuming more memory.
The query that go the most was this one (nearly 500 times in one example):
SELECT "base_table"."id" AS "id", "base_table"."id" AS "base_table_id" FROM "group_relationship" "base_table" INNER JOIN "group_relationship_field_data" "group_relationship_field_data" ON "group_relationship_field_data"."id" = "base_table"."id" WHERE ("group_relationship_field_data"."gid" = :db_condition_placeholder_0) AND ("group_relationship_field_data"."entity_id" = :db_condition_placeholder_1) AND ("group_relationship_field_data"."plugin_id" LIKE :db_condition_placeholder_2 ESCAPE '\\')
We do make use views a lot to bring in related Group content to nodes. But that is the same as what we had with 1.x. I don't have any noticeable issues locally. Any suggestions about how to approach this? Has anyone else experienced it?
This is possibly related to # 3399969 → ?
Closed: duplicate
2.2
Code
In looking further this definitely related to 3399969. So am going to make some comments in that thread.