On Tue, Apr 09, 2013 at 02:17:38PM -0700, Gavin Spomer wrote:
> When you say "it will hammer web servers out there", are you talking about
> the web server the link checker (SubjectsPlus) is running on, the web
> servers of the links that are being checked or both?
The web servers of the links that are being checked.
> Since my code checks
> one link after another, not simultaneously, I don't think it's really
> hammering anything per say. It just takes time.
You're right; that was a gross exaggeration -- I'm sorry.
> I'm happy to make a special version for you that will randomize the order
> in which links are checked and/or pause between checks, if you think it
> will help. Honestly, I don't think it will.
Thanks. I wouldn't use a link checker in SP, so there's no need, but I
appreciate the offer.
Here's why I have a knee-jerk reaction to link checkers, if anyone is
interested in my tale of woe -- if 20 people in a classroom click on a
link to a record in our OPAC within a span of a couple of seconds, our
OPAC goes down. It's ridiculous but true. A link checker checking
links in SP to records in our OPAC has the same effect -- if it checks
20 in a row. If it randomizes all the links it checks, then the 20 are
likely to be spread out more and don't bring down our OPAC.
Bonus points to anyone who can identify the OPAC vendor. :-)