Slowness after updating to latest version
See original GitHub issueHello
I have been experiencing some issues like the slow switching between pages, after updating Piranha.
Previously I was using the synchronous
API on version 5.4 and there was no problem. Now, a single page reload takes 12 seconds and going to another page takes half of this.
Do you have any suggestions on how can this be fixed?
Thank you in advance.
Best regards, Chris
Issue Analytics
- State:
- Created 4 years ago
- Comments:15 (8 by maintainers)
Top Results From Across the Web
Is Windows 10 Slow After an Update? Here's How to Fix It
1. Restart Windows 10 · 2. Roll Back the Most Recent Windows Updates · 3. Repair Corrupted or Damaged System Files · 4....
Read more >Why did latest windows update slow down my computer?
After latest Windows update my computer has slow.
Read more >PC Slow after Windows Update? Here's How to Fix it?
In some cases, your computer might be running slow due to flawed update. For example; Windows 10 update KB4551762 caused processor and hard...
Read more >PC Slow After Windows Update? Here Are 8 Ways to Fix That
1. Uninstall the update · 2. Repair corrupt system files · 3. Clear Windows Update cache · 4. Optimize disk drives · 5....
Read more >Five tips to stop your computers slowing down after updates
Five tips to stop your computers slowing down after updates · 1. Regularly delete temporary files · 2. Keep startup processes low ·...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
And it all depends on how you’re using it. The official PiranhaCMS site runs 6.1 without any of these fixes without any negative impact, but in your case where you have a lot of referenced content from your page which causes a lot of operations there was a huge difference in performance!
The PageField was kept as is for backwards compatibility, but will be replaced in 7.0.
The cache implementation was a safety measure as users were destroying the cache instances by assuming they are new copies (which is a logical assumption).
In 7.0 there will be multiple instances of all cache services, one with clone and one without cloning.
So basically all the stuff you added will be out of the box functionality in 7.0, but is implemented the way it is in 6.0 for compatibility.
Best regards