-
Notifications
You must be signed in to change notification settings - Fork 639
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resaving entry in cp takes very long (~30sec) #9789
Comments
We are looking into a Neo-related performance issue (spicywebau/craft-neo#496), which may be related to your performance issue. Subscribe there to follow along. |
@brandonkelly Hey I think I also send a message to support regarding the same issues. |
I've also got clients concerned and it's managed to bring a shared staging server to a halt with the issue. |
I was able to repro this on a fresh test install with no plugins and matrix blocks alone. Submitted a new issue with some more information, hope it's helpful! #9802 |
For posterity, Craft 3.7.12 is out now with some performance improvements for saving entries (per #9802). If it’s still too slow, you may want to consider disabling draft autosaving, by setting the autosaveDrafts config setting to |
Description
Saving an entry takes about 30 to 60 seconds with a lot of duplicated queries (262 duplicated queries found out of 545). Most SELECT
id
,parentId
,volumeId
,name
,path
,uid
FROMcraft_volumefolders
.....Most duplicated queries come from craft_volumnfolders table.
in the queue.log we found the following lines, which gets repeated for the next ~30sec.
Updating the search index and stoping it right away (time.: 0.081s) 5:34 2021-09-02 17:25:54 [-][101][-][info][craft\queue\QueueLogBehavior::afterExec] [915959] Aktualisiere Suchindexe (attempt: 1, pid: 26012) - Done (time: 0.044s)
2021-09-02 17:25:54 [-][101][-][info][craft\queue\QueueLogBehavior::beforeExec] [915961] Aktualisiere Suchindexe (attempt: 1, pid: 26012) - Started
...
Steps to reproduce
Additional info
The text was updated successfully, but these errors were encountered: