Log In
Home
(0 votes) 8:17 am
Hi,
I’ve been using CyberSEO for months now without problems. Recently I moved one of my sites to VPS (CentOS 5.8 32bit + WHM/CPanel installed) 2048 RAM, and 2 dedicated cores of a Xeon processor.
Anyway, the site had ran without issues on a shared host for about 3 months. But because my site had become really busy (10000+ unique visits a day) they prompted me to upgrade. So I did, but ever since then CyberSEO is creating a big load on the server.
Everytime the cron-job starts running, it starts surging the cpu and crashing the whole server. How can this happen?
The weird thing is though, that when I manually select some feeds to pull, it runs and finishes the job without any issues.
Any suggestions?
11:33 am
I set pull-mode to “auto”. Apparently the pseudo-cron barely puts load on the server. Isn’t that weird?
11:24 pm
July 2, 2009
Online
Login to see the quote
Depends on your settings. How many feeds the plugin is trying to pull simultaneously? Do you have a synonym table? How large it is etc.
1:42 am
I don’t use synonym tables, php code or anything like that.
The only thing I use CyberSEO is to add rel=nofollow and generate a thumbnail, besides pulling the feeds.
I have about 16 feeds that I’ve added all at once through a settings-file, so all the timers countdown simultaneously and I don’t know of a way to regulate the number of feeds that’re pulled simultaneously.
It stays weird though that with wp-cron, he has no issues of taking on all 16 of them at the same time (it maybe raises the load by 0.15 points) and with cronjob it raises the load by 50+ points and completely takes down the whole server.
3:53 am
July 2, 2009
Online
Looks like there is something wrong with your cron settings. Perhaps it triggers too often or so. Otherwise there should be no overheads at all.
The plugin pulls 16 feeds, it does the following:
- downloads every feed from a remote host;
- parses every feed to extract the posts;
- check the existence of every post in the database;
- downloads all 16 images from the remote hosts;
- resizes the downloaded images and saves them locally as feature thumbnails;
- inserts every post into the WP database.
As you can see, this “simple” task may take a rather long of time.
4:15 am
Yeah, that sounds reasonable.
Where can I find the cron-settings? FYI: I run this version of CyberSEO on a VPS with cPanel/WHM installed. So if you could point me to the cron-settings, I could check it out.
On another note: I just started using the “Post date adjustment range” settings to schedule new posts randomly in the next 60 minutes after syndication. Which is an awesome feature by the way! :) The problem that arose though, was that all posts missed their schedule and never got published. Now I installed a plugin called “Missed Schedule Fix” which took care of that problem, but still… it seems that the pseudo-cron within Wordpress is broken. Don’t you think? Do you have any knowledge of this stuff? And even better, know a way of getting it fixed?
I think that if we manage to get the pseudo-cron fixed, that’ll also take care of CyberSEO never triggering the auto-pull. In other words, then everything will work as it should and I’d be a very happy camper! :P
6:17 am
I’m pretty sure I’m closing in on the issue: I installed WP-Cron Dashboard: a plugin that show what tasks the WP-cron plugin has scheduled.
I’m sure you understand this better than I do, but when I opened the list, first of all there were a few 100 scheduled tasks that didn’t run since earlier today when my server crashed.
The list is filled with things like this:
Entry #4: update_by_wp_cron X no action exists with this name
and
Entry #6: publish_future_post X no action exists with this name
No doubt about it that update_by_wp_cron is triggered by CyberSEO, right? Is that the function that is called when the feeds should be pulled? And then publish_future_post should be the function that is called when a scheduled post should be published. Right?
So, what does it mean that these functions don’t exist? Did they get lost somehow? How do I get them back?
11:16 pm
It appeared the problem was caused by WP_Cron. My explanation is, that because my site is pretty busy, multiple instances of WP_Cron are loaded, which will eventually cause a surge to the memory or cpu.
I defined wp_cron as disabled in wp_config which seemed to lower the load immediately. Then I added wp_cron as a regular cronjob to be run every 10 minutes (so he can accurately pick up scheduled posts and stuff) and the first thing I noticed was that posts scheduled by CyberSEO were picked up and published with ever cron-run.
I’m currently testing which will cause less load to the server: setting CyberSEO to auto-pull mode, so it goes along with WP-cron or having it run as his own cron-job every hour. I’m guessing the latter, but we’ll see about that.
—
Added the regular cronjob to my crontab and it ran silent without adding any load to the server. By the way, I’m super happy I found this schedule-function you inserted in the app. Till now I was using some crappy other app for that, which in the end was only messing up my database. So 1 more star for CyberSEO!!! :)
All RSSMost Users Ever Online: 541
Currently Online: CyberSEO
10 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
ninja321: 84
s.baryshev.aoasp: 64
Freedom: 61
MediFormatica: 49
B8europe: 47
saviulisse67: 45
Member Stats:
Guest Posters: 338
Members: 2641
Moderators: 0
Admins: 1
Forum Stats:
Groups: 1
Forums: 5
Topics: 1538
Posts: 7761
Newest Members:
stproducties, thiago_barbosa, maxus.ix, marino.costa.gonzalez, christian.501pressurewashing, kevin.crywolfAdministrators: CyberSEO: 3679