Pingback Clobbers Server
Reported by Aaron | June 22nd, 2008 @ 03:15 PM
When pingbacks are enabled the server gets clobbered. the wcpu for that httpd thread increases to 100%. Also, I have wp-o-matic updated every hour, and the first thread isn't complete by the 2nd and it just stacks up. Soon the server load is > 75.
There are a couple of ways to fix it.
The first is to create a lock system so that a feed is being processed more then once at same time. This would fix some duplicate issues I noticed as well.
Another is to optimze the pingback system, which seems outside this scope. However you could thread this process. So that it updates the blog with the new posts. Then launches the pingback system afterwords.
Comments and changes to this ticket
-
Tony June 25th, 2008 @ 09:40 AM
- Tag cleared.
I've experienced this issue too... I'm disabling pingbacks on my campaigns to see if that helps. Thanks for reporting it Aaron.
-
Guillermo Rauch July 18th, 2008 @ 10:12 AM
- State changed from “new” to “invalid”
Maybe... in the future, WP-o-Matic should work with a standalone daemon. But for now, there's nothing I can do.
-
Aaron July 18th, 2008 @ 12:10 PM
Well, what I would do, is write a locking system. IE a flag in the campaign table. So at the start of the update process it sets it as true, then when it finishes it sets it as false. So that when you start the campaign you look at that flag. If it's set to true skip it.
This would create some problem with the campaign getting stopped inadvertently but, you could have an interface to tell if the campaign is locked. If it is a way to reset it.
-----Original Message-----
From: Lighthouse [mailto:support@lighthouseapp.com]
Sent: Friday, July 18, 2008 7:12 AM
To: aaron.pike@aspiretoachieve.com
Subject: [WP-o-Matic #28] Pingback Clobbers Server
-
Aaron July 18th, 2008 @ 12:20 PM
The idea, is keep processes from stacking up. 1 process in a loop is bad. But, if you have this croned every 30 mins or hour even. By the end of the day, you got a bunch of processes stacked up and the box load is very high. Not only is the box load high, but I've seen it keep importing the same posts over and over again every cron. Which leads me to believe, the process hangs somewhere after the post but before the hashing. The locking won’t fix that, but it will keep the box manageable when it does happen.
-----Original Message-----
From: Lighthouse [mailto:support@lighthouseapp.com]
Sent: Friday, July 18, 2008 7:12 AM
To: aaron.pike@aspiretoachieve.com
Subject: [WP-o-Matic #28] Pingback Clobbers Server
-
Ricardo Rauch April 15th, 2010 @ 08:49 AM
- Assigned user changed from “Guillermo Rauch” to “Ricardo Rauch”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
WP-o-Matic project.
People watching this ticket
Aaron
Referenced by
-
28
Pingback Clobbers Server
Subject: [WP-o-Matic #28] Pingback Clobbers Server
-
28
Pingback Clobbers Server
Subject: [WP-o-Matic #28] Pingback Clobbers Server