-
Posts
-
I have just installed a fresh WordPress install. As I upload the latest Enfold 2.9.2 and activate it, Debug bar shows Memory usage at a whopping 81Mbs!! ( 81,779,824 bytes )
When I deactivate to a default theme, it lowers to 19Mbs (19,505,744 bytes).
This is pre-migrating my site’s content to a new optimized host. The only variable is Enfold.
What is this memory footprint? I have been shown that an optimized WP is at between 15-20Mbs for memory. Quadruple is not doable.
I have checked another clients’s site with Enfold and it is around 45-50Mbs. Still double standard size. I do not know why the variation here. I’ve measured all plug-ins on sites using P3 Profiler and with the exception of WooCommerce at 5Mbs, the rest are all under 2Mbs – including LayerSlider standalone.
How to reduce or troubleshoot this? Enfold is so user-friendly, I cannot believe it’s coded such that it would be so out of the range on memory.
I have posted previously about performance issues and glitches since the WP4 upgrade and latest version of Enfold. Is the AVIA Framework compatible with WP4? Are there compatibility issues with LS, Avia Framework, WP4, Yoast SEO being workedd on and soon to be updated?
Is there a known conflict that is causing such a huge memory footprint?
All was smooth sailing for all my Kreisi theme sites for 6 months til recent updates. This would explain – some conflict with framework and latest WP update that is causing excessive memory usage -why theme sites (for myself and clients) are so slow since the last update. Any suggestions on how to amend?
I like others on the forum here, am considering strongly to revert all my sites to a WP3.9, Enfold 2.8 or 2.9 version state today, til a theme update that is more stable, without conflicts on WP4. Is this forthcoming? Is there a set date for an update to Enfold (and other themes) now that a series of bugs and conflicts are coming out on the forums from live site issues??
This is a temporary fix at most, until an Enfold 3 update that addresses this memory issue, performance shift, LayerSlider bugs (new updated version), and the Yoast SEO conflict.
Are there others experiencing these issues? And specifically with Memory usage here?
Again, this is for a fresh install of WordPress4 with the theme uploaded via ftp, as with plug-ins, with a resulting 81MBs, with the same plug-ins and install, but only Enfold deactivated, there is a 60Mbs decrease.
Any assistance in troubleshooting present Enfold issue appreciated. Would love to have Enfold working stably and smoothly on WP4.
Michael
Hey Michael!
Just to clear up any misconceptions, WordPress 4.0 and Enfold version 2.9.2 have no conflicts. We have had 2-3 actual small bugs that have not warranted a bug fix release for the entire user base. As with just about every WordPress update where an internal js file was changed there are lots of caching issues that go along with updating that make it seem like odd errors are happening but eventually go away.
As for the main question, The memory footprint is higher because it uses a lot of ajax. That would be my only guess. I’ve installed hundreds of client sites, maintain quite a bit at the same time. Even using an extremely stripped down _s created theme I’m getting around 30mb of memory usage compared to my live dev install of Enfold that stands around 50.
If you look at what the theme is doing it is not a surprise that the memory needed is higher. In addition I’ve not noticed any increase since switching all my sites to 2.9.2 and now the beta version of 3.0 for a few of them.I’ve never seen any installation go up to 80mb however.
I’m using Query Monitor when testing in this case and checking with both WooCommerce and BBPress active on my enfold dev install and neither is active on my second _s theme.
Cheers!
DevinThank you for your clarifications, Devin. Your answers are always so clear. It is very much appreciated.
I hope my previous comments of trying to resolve this issue – and other recent with LayerSlider – were not too infused with the frustrations of troubleshooting for days. I had been working and profiling my whole sites element by element – themes then individual plugins – to reduce the memory footprint before migrating to a new high speed, optimized host. The memory was coming out so high, astronomically at moments, and surprisingly so for these themes. It is of course obvious that the resource rich theme would have some increase in memory, but this was way beyond.
Anyways, your message came right when all cleared. Finished the migration of my site from Media Temple to Synthesis last night, and with an upgrade of my servers to php 5.5 during the night, the memory footprint is now 13,526,448 bytes! (13.5Mbs) for the same site.
New host and latest php did it.
Surprisingly, my home layer slider which has not been appearing in Safari on all my Enfold sites this past week (or longer), now appears upon this successful migration and upgrade. I do not know how the server would make a difference in what seems a browser or LS, or latest LS integration bug, but it did in this instance.
I take it the integration of the latest version of LS into Enfold is awaiting the Enfold 3 update. Release date?
Thanks again. All best…
MichaelGlad to hear its cleared up. Server specs can make a huge difference and it is easy to forget that its all running on hardware somewhere.
3.0 was updated with LayerSlider 5.1.2.
Yes. Tremendous difference with server in this case. Another site on Flashlight that has been having timeout and response issues for a month since WP4 update, etc. – sometimes a 2 sec response, or 30+ secs, or none, now on the new server clocks in at 434ms. It turns out Media Temple had degraded. Highly recommend Synthesis for anyone looking for a great platform for their WP sites.
I think a major difference with the memory was the php version, so getting a server with 5.5 was key. I feel their were issues with LS with previous versions, and additional queries were creating the monster memory foot. So LayerSlider with latest php, and of course a fast and steady server as the resolution. SpeedBooster plug-in, when not with precise settings – and now redundant on new host – was creating issues with LS.
Just info for others who it might assist.
Enfold 3.0 comes with LS 5.1.2? Enfold 2.9.2 is with LS 5.2, and the latest version of LS is 5.3.1. Is this correct? Or is that the most stable version of LS in final evaluation. Would appreciate clarification there, and then this thread can be closed and resolved.
Thank you for the support.
- The topic ‘Memory Footprint Issues with Enfold’ is closed to new replies.