Skip to content
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

Upgrading craftcms causes the cms system to load and save very slowly #10759

Closed
dsfofwuc opened this issue Mar 16, 2022 · 5 comments
Closed

Upgrading craftcms causes the cms system to load and save very slowly #10759

dsfofwuc opened this issue Mar 16, 2022 · 5 comments

Comments

@dsfofwuc
Copy link

Description

We upgraded from craftcms3.4 and craft-neo2.5.10 to craftcms3.7.30 and neo2.12.5 and found some problems. After the upgrade,but the craftcms page is very slow to load, save data is also very slow and save Entries 504 time out,We have set php.ini memory_limit=-1, max_execution_time=120.

Steps to reproduce

1.upgrade craftcms

Additional info

  • Craft version:3.7.30
  • PHP version:7.3.4
  • Database driver & version:5.5.0+
  • Plugins & versions: "craftcms/aws-s3": "1.3.0",
    "craftcms/cms": "3.7.30",
    "craftcms/redactor": "2.10.2",
    "creativeorange/craft-article": "1.0.5.1",
    "fruitstudios/validateit": "1.0",
    "spicyweb/craft-neo": "2.12.5",
    "vlucas/phpdotenv": "3.4.0"
@dsfofwuc dsfofwuc added the bug label Mar 16, 2022
@brandonkelly
Copy link
Member

Draft and revision creation is known to slow the entry editing experience down a bit – see the discussion at #9802. You can opt out of automatic draft creation by disabling the autosaveDrafts config setting. And you can also consider disabling versioning from your sections’ settings, if it’s not necessary.

Good news is that both draft and revision creation are much faster in Craft 4 (see #10577 + #10589). It’s currently in beta, and the first stable release will be in just a few weeks, on May 4.

@dsfofwuc
Copy link
Author

@brandonkelly
When saving the entry, 504 will appear in about 1 minute, and it will be refreshed and saved, which will affect our work efficiency; this has always been the case after I upgraded, and I have tried various php and nginx configurations. suggestion, thanks

@angrybrad
Copy link
Member

@dsfofwuc If you want to write into [email protected], we can try to help you get past the 60-second timeout in your environment as a stop-gap until you're able to upgrade to Craft 4.

@dsfofwuc
Copy link
Author

@angrybrad Can you give me some ways online? The project is now online, it is very urgent, thank you

@brandonkelly
Copy link
Member

@dsfofwuc It is going to depend on your environment. Please email [email protected].

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants