1 to 7 of 7
OIOpublisher is using a ton of resources on my blog (www.BiotechBlog.com). I've read a previous thread on the matter: http://forum.oiopublisher.com/discussion/347/out-of-memory-problem/#Item_0 and it appears that while OIOpublisher is designed be very light on resources, that may not always be the case.
I am using v2.07. I get the following errors on my Wordpress dashboard:
- In the "stats" box, I get: Fatal error: Out of memory (allocated 64487424) (tried to allocate 35 bytes) in /home/thinkbio/public_html/biotechblog/wp-content/plugins/oiopub-direct/include/cache.php on line 39
- In the "plugins" box, I get: Fatal error: Out of memory (allocated 45613056) (tried to allocate 16 bytes) in /home/thinkbio/public_html/biotechblog/wp-content/plugins/oiopub-direct/include/cache.php on line 39
When I activate the PluginHogDetector plugin (http://money.bigbucksblogger.com/) it indicates that my header takes between 7 and 12 seconds to load. If I deactivate OIOpublisher, that drops to 0.40 seconds.
So, given that my OIOpublisher installation is exceeding memory limits and slowing my blog. What can I do to diagnose the fault and fix the problem?
If you look at the last post in that other thread, you'll see that it wasn't OIO that was causing the problem. It was actually a problem with the database not being optimized (which produces memory overhead).
The only thing worth checking on the OIO side of things is the number of rows in the oiopub_config table in the database. There shouldn't be more than 100 or so, but one install did end up with a few thousand rows - which would use quite a bit of memory upon loading. If you find something similar, let me know.
-------
If the config table doesn't have a large number of rows, I'd advise following the procedure the other postser did: optimize your database using phpmyadmin, then deactivate other plugins to see whether the error still occurs.
Remember, the more plugins you have, the more likely you are to reach the memory limit (as it is cumulative).
You've found the problem -- I have 79,360 rows in my wp_oiopub_config table. It seems that a lot of them have the name "cron running" and zero-values for value and api_load. How do I fix this?
Thanks.
In addition, you can also check the amount of memory OIO is using in general by adding oio-debug=1 to the end of the url in the admin area.
For example:
http://demo.oiopublisher.com/wordpress/demo-admin/?oio-debug=1
For now, run this query:
DELETE FROM wp_oiopub_config WHERE name='cron_running' AND value='0'
Then re-upload the latest code, and give it a few hours to see whether the number of db rows in that table creeps back up again. I'll check on the cron code in the mean time.
Header load times dropped to ~3 seconds when I deleted the extraneous database entries.
After uploading the new code (v2.08), header load time is ~1 second.
Looks like it's behaving.
Thanks for the rapid resolution.
No problem - just keep an eye on the number of rows in the near future.
You're now the 2nd person to report such behaviour, so whilst it doesn't appear to be a widespread problem, it could still be a problem on certain setups.
1 to 7 of 7