Search Results for 'memory'

i have 256 in the memory and i disable all plugins and the problems its still there

Wow. 7 seconds is a lifetime ! It might be due to running a proxy? A lot of folks running nginx (we’re running Apache, and then nginx for SOME things not all) seem to run through a proxy, and that might cause the issue. Perhaps check amount of memory allocated to PHP ? I think mine is set to 512MB, with 256M being typically the best lower limit for WP these days. I think you already checked that.

If you can see a noticeable slowdown running that just from the server, two things you might try is a traceroute between the API IP and your DNS, and/or check with your hosting provider to explain the issue. It might be something they have run across before.

Or it could be some weirdo voodoo thing like why my stupid Font Awesome 4 CSS don’t load consistently off Amazon’s CDN, or from the free CDN that also hosts bootstrap. Gave up on that one 🙂

The solution we use is called Auto Post Thumbnail PRO which is also available super cheap via Envato/Themeforest.

It will automatically make first image in post the featured image, and also works if it’s a video only post, and you can set a default image, and regenerate (check memory setting, or it will just stop about about 300 items). Works great.

Yeah. IN the old days theme developers had to use one of two plugins to do the thumbnails, or write custom hooks into server imagemagick libraries or similar. Then WordPress finally added thumbnail support “if you make it featured image” … and then all the theme devs stopped using the old plugins. We have one from 2006-2010 that let us specify the exact cropping and would pull from YouTube and stuff … huge memory hog, but we’ve always had our own server(s), so wasn’t issue. Also, for a long time the WordPress folks didn’t actually run any magazine or content sites beyond blogs, so it took years to add CMS features to the “blogging platform.” And there are still some really dumb things in there one should be able to fully turn off and remove, or do by default. “Crop direction” is a really needed thing for WP to add. Much like ability to grab thumbnail from first image in post regardless of “featured” or not. (Sigh.) Welcome to my world 😉

First thing you can do is set those sizes under WP-admin > settings > media – or the small, medium and large thumbnail sizes. This will minimize thumbs created by both the theme and WordPress. I think the thumbs are in the functions.php file if memory serves, but likely Marius will have more specific info on that. 🙂

Well got it sorted out, and it was a metter of PHP handling by Media Temple:

– I had to disable Fast CGI and process evertyhing in CGI
– I disabled NGINX processing as well
– Reseted the permalinks and downgraded to Yoast SEO 1.4, and all works fine

What a wild ride and weird issues, thank you all for your help!

Hey, did you check your wp-config.php file? I had similar isue a while back and found out a huge junk string has been added to the php file. That caused the dashboard to break down and heavy resource usage while loading

Really, anyone, help. Completely baffled. Anyone willing to help me getting this issue resolved?

I’ve tried everything, literally. And nothing works. Some of the back ends of the sites that use this theme work partially, some don’t even load at all. But the front end, loads perfectly.

I’m completely lost, really. Need some guidance…

@jbenbitez
not sure if you use a dbase optimizer for your site, but one thing I do after any major updates every time is
1) resave permalinks (just because)
2) run wp-optimize plugin to clean up dbase

We’ve been able to lessen the load on all our sites by as much as 20% (we have a LOT of pages) by using wp-optimize regularly, and also editing the wp-config to limit number of draft saves, and longer time to save each.

In our case the “BIG” memory leak was from YOAST. Going backward on one site fixed it, and on another getting latest version.

One client site was crashing until we stopped using AddThis “layers” plugin and cleared the cache about five times (not running Newspaper). GoDaddy hosting on that one.

Anyway – this is just some feedback on our issues- again, perhaps not related in any way to your issue. Often you can look at your site “error logs” to see what is generating an error, as best place to start with this kind of thing.

I’ve tried all Radu, reverting to Yoast 1.4, disconnecting all plugins and nothing has worked. This is a very very very strange thing and started since I updated to 3.4 and also updated Yoast to the latest version. Any help? I can’t publish anything on sites, when I get the to load the back end…

Do you need any admin data? I’ll be more than happy to provide full access to anything you might need, thank you!

Be aware Yoast SEO had a big memory leak issue that raised our server processes by 30x on one of the 1.5x versions; and various other issues. We reverted to 1.4x due to that while they get their act together – might not be issue on your site, but see my other thread on that. Jetpack also had a recent update, and some folks had issues with that.

Might not be related — but this stuff is from the past 2 weeks, specifically.

And also, I don’t keep previous versions of the theme, where can I get them?

Well, I keep everything up to date, I updated to the latest version of the theme and of the plugins that I use (that include jetpack, Yoast SEO and W3). Nothing else was changed on the server, it’s a DV from media temple so resources are not an issue… And also allocated more memory to the install (256MB) and nothing… Now the problem is also in another site were the backend is slow as a snail.

Any help? Very much needed…

hi,
did you change something on that site?
did you make an update to a newer version of the theme or a plugin?
if this is the case can you downgrade to the priveus version.

if this is not then case then what change? did you talk with your hosting company did they change something.

Thanks for you message.
Radu A.

There have been a LARGE number of bugs with the Yoast SEO plugin released last week (1.5), and about three or four patches so far. Still buggy as hell with 1.5.2.3 (including option for Google News keywords not saving to dbase or showing in the SEO post panel). I rolled back my sites to the prior version (stable), 1.4.25 due to a lot of issues including a major memory spike on our server post 1.5 update. If you look at the changelog for 1.5 it’s pretty awful, and doesn’t bode well for their new development team, frankly.

SERIOUSLY …. (!)

— YOAST SEO 1.5 BUG FIXES (SO FAR) —

1.5.2.3

** Note: if you already upgraded to v1.5+, you will need to retrieve your Facebook Apps again and please also check your Google+ URL. We had some bugs with both being escaped too aggressively. Sorry about that. **

◾Bugfixes
◾Added missing settings menu pages to wp admin bar.
◾Replaced old AdWords keyword tool link.
◾Fix wp admin bar keyword density check link
◾Taxonomy sitemap will now also show if empty.
◾Prevent infinite loop triggered by sitemap_close(), fixes #600 as reported and fixed by pbogdan.
◾Fixed a link count Page Analysis bug.
◾Fixed a keyword density problem in the Page Analysis
◾Fixed OpenGraph/GooglePlus/Twitter tags not showing in a select few themes, issue #750 as reported by Jovian and wwdboer – props Jrf.
◾Fixed Facebook Apps not being saved/ “Failed to retrieve your apps from Facebook” as reported by kevinlisota in issue #812 – props Jrf.
◾Fixed duplicate feedback messages on WPSEO -> Social pages as reported by steverep in issue #743 – props Jrf.
◾Flush our force title rewrite buffer earlier in wp_footer so it can be used by other plugins in wp_footer. Props Gabriel Pérez Salazar.
◾Start the force rewrite buffer late (at 999) in template_redirect instead of get_header because of several themes not using get_header, issue #817 as reported by Jrf.
◾Fixed ‘Page %d of %d’ / %%page%% variable not being replaced when on pages, as reported by SGr33n in issue #801 – props Jrf.
◾Restore robots meta box per post to its former glory, it now shows even when blog is not set to public.
◾Fixed individual page robots settings not being respected when using a page as blog as reported by wintersolutions in issue #813 – props Jrf.
◾Fixed: Too aggressive html escaping of the breadcrumbs.
◾Fixed: Last breadcrumb wasn’t always determined correctly resulting in crumbs not being linked when they should have been.
◾Fixed: Breadcrumbs were sometimes missing separators and default texts since v1.5.0.
◾Fixed: 404 date based breadcrumb and title creation could cause corruption of the $post object.
◾Fixed: Filtering posts based on SEO score via the dropdown at the top of a post/page overview page no longer worked. Fixed. As reported by gmuehl in issue #838 – props Jrf.

◾Enhancements
◾Added filters for the change frequencies of different URLs added to the sitemap. Props to haroldkyle for the idea.
◾Added filter wpseo_sitemap_exclude_empty_terms to allow including empty terms in the XML sitemap.
◾Private posts now default to noindex (even though they technically probably couldn’t be indexed anyway).
◾Show a warning message underneath a post’s robots meta settings when site is set to noindex sitewide in WP core.
◾Updated licensing class to show a notice when requests to yoast.com are blocked because of WP_HTTP_BLOCK_EXTERNALS.

◾Other
◾Refactored the breadcrumb class – props Jrf.

1.5.2.2

◾Bugfixes
◾Fix for issue with Soliloquy image slider was not applied to minified js file.
◾Fixed some PHP ‘undefined index’ notices.
◾Fix banner images overlapping text in help tabs.
◾Fixed meta description tag not showing for taxonomy (category/tag/etc) pages as reported in issue #737 and #780 – props Jrf.
◾Prevent a fatal error if wp_remote_get() fails while testing whether the title needs to be force rewritten as reported by homeispv – props Jrf.

◾Enhancements
◾Added composer support – props codekipple and Rarst.

1.5.2.1

◾Bugfixes
◾Fix white screen/blog down issues caused by some (bloody stupid) webhosts actively disabling the filter extension – props Jrf.
◾Fix for some PHP notices, issue #747 as reported by benfreke – props Jrf.
◾Fixed: GooglePlus vanity urls were saved without the + as reported by ronimarin in issue #730 – props Jrf.
◾Fix WP Admin menu items no longer clickable when on WPSEO pages as reported in issue #733 and #738 – props Jrf.
◾Fix strict warning for W3TC, issue 721.
◾Fix RSS text strings on options page being double escaped, issue #731 as reported by namaserajesh – props Jrf.
◾Avoid potential confusion over Facebook OpenGraph front page usage, issue #570 – props Jrf.
◾Potentially fix issue 565 bbpress warning message. Thanks inetbiz for reporting and tobylewis for finding the likely cause.
◾Filter ‘wpseo_pre_analysis_post_content’ output is now only loaded in DOM object if not empty. – props mgmartel.
◾$post_content is now unset after loading in DOM object. – props mgmartel.
◾Fix Alexa ID string validation, as reported by kyasajin and Bubichka in issue 736 – props Jrf.
◾Fix issue with Soliloquy image query, as reported by osalcedo and mattisherwood in issue #733 – props Jrf.

◾Enhancements
◾Twitter metatag key is now filterable by ‘wpseo_twitter_metatag_key’.
◾Added a filter called “wpseo_replacements” in wpseo_replace_vars to allow customization of the replacements before they are applied – props martinernst.
◾Added useful links for page analysis – props bhubbard.

◾i18n Updates
◾Updated nl_NL, id_ID, it_IT, fr_FR and de_DE
◾Added ko
◾Updated .pot file.

1.5.2
◾Bugfix: ◾If mbstring extension isn’t loaded, fatal error was thrown.

128MB increase in memory limit didn’t help.
Googling for other clues 🙂

OH…did you increase the php memory limit on the site ?
128MB is a good place to start if your host allows that high a limit.

If you have a virtual server or dedicated server try even higher, like 256MB.

I will be retrying W3 cache soon. Not today 🙂

Let me know how it goes for you, and update here!

• This reply was modified 12 years by simchris.