Search Results for 'memory'

I am finding I need to set my PHP memory to 128MB vs 64MB default with the new version of Visual Composer. Bigger site 256MB, heavy duty site, 1GB. Massive site 4GB.

Something is wrong with the new version of the Visual Composer plugin. My site runs normally on 35-40 mb ram. With the new version it was 135-150 mb. I have uploaded the plugin version from Newsmag 1.4. Now I have again 35-40 mb memory and the site is fast again (with Newsmag 1.5)…

Sadly I have tried that.

Even rebooted the server.

I have lots of memory free: Memory : 81.47 of 128

I have tried to reinstall the Visual Composer even.

I don’t want to hijack this thread. Do you want me to create another?

I don’t know how to clear cache of wordpress or theme, please say me.

Yesterday I explained to hosting my problem and in the server log there’s a php memory errors (this is from this morning):

[Tue Feb 03 10:32:27 2015] [warn] [client xx.xxx.xxx.xxx] mod_fcgid: stderr: PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 7680 bytes) in /xxx/xxxxxxx/xxxxxx/ildragoparlante.com/public_html/wp-includes/class-feed.php on line 39, referer: http://ildragoparlante.com/wp-admin/

I send it now you warm about admin-ajax.php.

I don’t have any problems or errors on saving options in the theme panel when jetpack and seo plugins are disabled.

load-sc...ver=4.1 (riga 4)
POST http://ildragoparlante.com/wp-admin/admin-ajax.php

200 OK
558ms
load-sc...ver=4.1 (riga 4)


• This reply was modified 11 years by SilvioTO.

I am reluctant to update the theme now. Why does the Visual Composer use so much more memory? The whole changing of VC element names or running an SQL command isn’t something I want to do, because if it goes south, I don’t want to be left with a non-working web :-/

I also have this problem! The new visual composer plugin uses too much memory.

This is in my errors in cpanel, maybe will help>

[Fri Jan 23 22:56:34.333856 2015] [:error] [pid 287451] (12)Cannot allocate memory: [client 74.125.40.23:52600] couldn’t create child process: /opt/suphp/sbin/suphp for /home/aktuelno/public_html/index.php
[Fri Jan 23 22:53:49.907189 2015] [:error] [pid 271908] (12)Cannot allocate memory: [client 77.28.65.51:51873] couldn’t create child process: /opt/suphp/sbin/suphp for /home/aktuelno/public_html/index.php, referer: http://aktuelno24.mk/
[Fri Jan 23 22:53:49.906964 2015] [:error] [pid 271908] (12)Cannot allocate memory: [client 77.28.65.51:51873] couldn’t create child process: /opt/suphp/sbin/suphp for /home/aktuelno/public_html/index.php, referer: http://aktuelno24.mk/
[Fri Jan 23 22:52:32.234782 2015] [:error] [pid 242706] (12)Cannot allocate memory: [client 213.135.187.20:51403] couldn’t create child process: /opt/suphp/sbin/suphp for /home/aktuelno/public_html/index.php

Not a “problem” with Varnish; we just had the other caching options pre-installed with our setup and just needed to implement them, and no reverse proxy stuff. Also mod_pagespeed already had a function to connect to memcache for speedup, so it made the most sense than experiment with Varnish.

Lots of folks do use it however.

re: Memcached:
Websites using Memecached:
Wikipedia
Flickr
Twitter
Youtube
Digg
WordPress.com
Craigslist

Websites using Varnish:
BBC Wired Vimeo Zappos MorningStar Business Insider Thinkgeek

old article I’m quoting fyi, on “who uses”….
http://www.neonrain.com/blog/web-cache-apc-vs-memecached-vs-varnish

I should also mention we’re using the memory based caching because we have 32GB RAM on our dedicated server 😉

• This reply was modified 11 years by simchris.

IE 6 and 5 are not supported but some features “might work” for some folks.

Note the list of “supported” browsers on ThemeForest for his theme. IE8 is the earliest version supported, if memory serves.

Almost nobody supports IE6 and older as those browsers are no longer secure.

Hi Chris, the problem is with Yoast WordPress SEO and if memory serves me correctly you alos had problems wiht this plugin in the past.

Marius,

I discovered that the php accelerator (APC) was causing some issues (double calls and memory errors). I’ve switched to eAccelerator and it seems to have resolved the issues.

Philip

So, I received your file, but haven’t been able to import it. I keep receiving the following error:

“File is empty. Please upload something more substantial. This error could also be caused by uploads being disabled in your php.ini or by post_max_size being defined as smaller than upload_max_filesize in php.ini.”

Now this seems to be an issue that indicates the PHP setup is inadequate for what I’m trying to do. This is how PHP is setup on 1&1 wordpress accounts:

PHP 5.4
allow_call_time_pass_reference – not supported
allow_url_fopen – active
display_errors – active
error_reporting – 22517
html_errors – active
include_path – .:/usr/lib/php5.4
log_errors – deactivated
magic_quotes_runtime – not supported
magic_quotes_sybase – not supported
max_execution_time – 20
memory_limit – 30M
post_max-size – 8M
prescision – 14
safe_mode – deactivated
short_open_tag – active
upload_max_filesize – 40M
zend framework – v2.4.0

I think the problem is with those settings.

I’m on a shared 1&1 account, but I have manually installed the normal wordpress (not using the 1 click installer). I can upload a php.ini. However I am not allowed to use SSH in order to make an uploaded php.ini recursive, which means that I have to manually upload a php.ini to wherever the importer does something. Since I do not know where that may be, I have gone ahead and copied a php.ini to any place that has .php files and even some additional ones (like upload folder).

This is how my php.ini looks:

<?php
/**
 * Custom WordPress configurations on "wp-config.php" file.
 *
 * This file has the following configurations: MySQL settings, Table Prefix, Secret Keys, WordPress Language, ABSPATH and more.
 * For more information visit {@link http://codex.wordpress.org/Editing_wp-config.php Editing wp-config.php} Codex page.
 * Created using {@link http://generatewp.com/wp-config/ wp-config.php File Generator} on GenerateWP.com.
 *
 * @package WordPress
 * @generator GenerateWP.com
 */

/* MySQL settings */
/* define( 'DB_NAME',     'database_name_here' );
/* define( 'DB_USER',     'username_here' );
/* define( 'DB_PASSWORD', 'password_here' );
/* define( 'DB_HOST',     'localhost' );
/* define( 'DB_CHARSET',  'utf8' );

/* MySQL database table prefix. */
/* $table_prefix = 'wp_';

/* Authentication Unique Keys and Salts. */
/* https://api.wordpress.org/secret-key/1.1/salt/ */
/* define( 'AUTH_KEY',         'put your unique phrase here' );
/* define( 'SECURE_AUTH_KEY',  'put your unique phrase here' );
/* define( 'LOGGED_IN_KEY',    'put your unique phrase here' );
/* define( 'NONCE_KEY',        'put your unique phrase here' );
/* define( 'AUTH_SALT',        'put your unique phrase here' );
/* define( 'SECURE_AUTH_SALT', 'put your unique phrase here' );
/* define( 'LOGGED_IN_SALT',   'put your unique phrase here' );
/* define( 'NONCE_SALT',       'put your unique phrase here' );

/* WordPress Localized Language. */
/* define( 'WPLANG', '' );

/* PHP Memory */
define( 'WP_MEMORY_LIMIT', '64' );
define( 'WP_MAX_MEMORY_LIMIT', '40' );
php_value upload_max_filesize 32M
php_value post_max_size 40M
ini_set('max_execution_time', 300); //300 seconds = 5 minutes

/* Zip Compression Activation

zlib.output_compression = On

/* Absolute path to the WordPress directory. */
/* if ( !defined('ABSPATH') )
/* 	define('ABSPATH', dirname(__FILE__) . '/');

/* Sets up WordPress vars and included files. */
/* require_once(ABSPATH . 'wp-settings.php');

I still get the same error though, so I have tried a few other things:

1. Changing the .htaccess file to include the change to php limits -> leads to the site being offline, giving me an error 500 page.

2. Using various other php.ini files with different code snippets from various sites and wordpress threads -> Same error, still no cigar.

3. Uploading a gzip file -> I receive a no WXR XML data error message.

4. Allowing czip compression in php.ini and uploading the zip -> Memory exceeded = Memory error on line 460 in some .php file leading me to believe that this isn’t gonna work out either.

Now 1&1 suggests for me to get Cygwin and mirror my folder setup and then just tinkering around more with my php.ini, so that I at least do not have to find every single php.ini and manually change it to a newer version. They were of the opinion that my php.ini looks fine and it should work. They also swear to me, that I have the rights needed for adding the php.ini (meaning it should be effective).

I am running out of patience here and still haven’t come one bit closer to being able to actually import the .xml I received.

Does anybody have any idea as to what I am doing wrong here or what else I could try in order to finally get a successful import of the full demo content?

Regards

Peter

• This reply was modified 11 years by Petewashere.
• This reply was modified 11 years by Petewashere.
• This reply was modified 11 years by Petewashere.

Hmmm…. likely you could make a new “category” that doesn’t conflict with the page name, then delete old category and redirect to the new category (WP gives you option when deleting category to point at a replacement category, if memory serves — might be a plugin for that I’m thinking of …); then try deleting the page, then create a NEW page.

Likely also running WP-Optimize after doing backup might help, and perhaps using the built-in WP repair dbase function I think you can do by adding a line to your wp-config.php file if memory serves (sorry, been down these roads a few times the past 9 years, but some of it rusty in my fragile little mind …) 🙂

We’re running PHP Version 5.4.22 on our server and have been using Newspaper the past year without any issues related to PHP. Also running one site with Newspaper with https with zero issues.

It sounds more like a system setup issue on the backend as far as resources, memory allocation, caching, or possible DNS issue; and not the PHP “version” itself being the issue with the theme/WordPress.

While not common in the past, if you’re using one of the tricky *new* setups with SSL and a shared IP, that can cause some intermittent things vs dedicated IP address.

Seems like you should have the overall system checked, as not being able to access your WordPress login is generally a sign something more notable is wrong.

thank you all boys 🙂

@themediumutm these are P3 results:
plugin: 24 (currently active)
Plugin Load Time 1,004 (sec. per visit)
Plugin Impact 65,8% (of page load time)
MySQL Queries 73

and WP query monitor:

Page generation time
9,1419
15,2% of 60s limit

Peak memory usage
95.159 kB
36,3% of 262.144 kB limit

Database query time
6,6556

Database queries
SELECT: 54
SHOW: 6

@lucian. i’ve deactived everything. you can take a look.
for the tagdiv speed plugin we’re slowly working on it, as we’re not so smart with coding. if you think this will resolve, we’ll ask for help and do it.

(btw, at least, yesterday we’ve upgradated to a more powerful hosting plan)

Well the server is ours,nothing shows in the logs of the server nor in the logs for the cpanel I have the memory on all sites set at 256m it only has three plugins the images are the right size And since I have built in virus scanners and spam checkers (server) I thought maybe you could figure out why with all the other sites working ok on the server you might have an idea as to why your theme is having problems thanks

hi, here is one of the plugins I mentioned which is supposed to help with tracking down where all the dbase queries are going … I’ve started using this recently to double check myself on stuff:

WORDPRESS QUERY MONITOR PLUGIN:

https://wordpress.org/plugins/query-monitor/

Query Monitor is a debugging plugin for anyone developing with WordPress. It has some advanced features not available in other debugging plugins, including automatic AJAX debugging and the ability to narrow down things by plugin or theme.

Here’s an overview of what’s shown:

Database Queries
◾Shows all database queries performed on the current page
◾Shows affected rows and time for all queries
◾Show notifications for slow queries and queries with errors
◾Filter queries by query type (SELECT, UPDATE, DELETE, etc)
◾Filter queries by component (WordPress core, Plugin X, Plugin Y, theme)
◾Filter queries by calling function
◾View aggregate query information grouped by component, calling function, and type
◾Super advanced: Supports multiple instances of wpdb on one page

Filtering queries by component or calling function makes it easy to see which plugins, themes, or functions on your site are making the most (or the slowest) database queries.

Hooks
◾Shows all hooks fired on the current page, along with hooked actions and their priorities
◾Filter hooks by part of their name
◾Filter actions by component (WordPress core, Plugin X, Plugin Y, theme)

Theme
◾Shows the template filename for the current page
◾Shows the available body classes for the current page
◾Shows the active parent and child theme name

PHP Errors
◾PHP errors (warnings, notices, stricts, and deprecated) are presented nicely along with their component and call stack
◾Shows an easily visible warning in the admin toolbar

Request
◾Shows matched rewrite rules and associated query strings
◾Shows query vars for the current request, and highlights custom query vars
◾Shows the queried object details (collapsed by default)

HTTP Requests
◾Shows all HTTP requests performed on the current page (as long as they use WordPress’ HTTP API)
◾Shows the response code, call stack, transport, timeout, and time taken
◾Highlights erroneous responses, such as failed requests and anything without a 200 response code

Redirects
◾Whenever a redirect occurs, Query Monitor adds an X-QM-Redirect HTTP header containing the call stack, so you can use your favourite HTTP inspector to easily trace where a redirect has come from

AJAX

The response from any jQuery AJAX request on the page will contain various debugging information in its header that gets output to the developer console. No hooking required.

AJAX debugging is in its early stages. Currently it only includes PHP errors, but this will be built upon in future versions.

Admin Screen

Hands up who can remember the correct names for the filters and actions for custom admin screen columns?
◾Shows the correct names for custom column filters and actions on all admin screens that have a listing table
◾Shows the state of get_current_screen() and a few variables

Environment Information
◾Shows various PHP information such as memory limit and error reporting levels
◾Highlights the fact when any of these are overridden at runtime
◾Shows various MySQL information, including caching and performance related configuration
◾Highlights the fact when any performance related configurations are not optimal
◾Shows various details about WordPress and the web server
◾Shows version numbers for all the things

Everything Else
◾Shows any transients that were set, along with their timeout, component, and call stack
◾Shows all WordPress conditionals on the current page, highlighted nicely
◾Shows an overview including page generation time and memory limit as absolute values and as % of their respective limits

Authentication

By default, Query Monitor’s output is only shown to Administrators on single-site installs, and Super Admins on Multisite installs.

In addition to this, you can set an authentication cookie which allows you to view Query Monitor output when you’re not logged in (or if you’re logged in as a non-administrator). See the bottom of Query Monitor’s output for details.

View your hosting account “error logs” to see why your site is ‘crashing’ …. perhaps a support ticket to your hosting provider to check logs might work, but you can usually see those logs from your hosting panel. If it’s shutting down ever NN hours that is usually due to something overloading, like not enough memory, too many plugins, images too large, runaway form script being used by spammers, etc.

Easy Social Share Buttons for WordPress – 0.2501 sec – 29.90% you should change that to a more light plugin like “Ultimate Social Deux”

Jetpack by WordPress.com – 0.0720 sec – 8.62% don’t know why people want this plugin on there site all it do is eat ur memory