If using the archive core module, a spider can really slow down a drupal site, by recursively following the "previous month" links on the archive calendar.
I saw that recently (a few Gigs of extra bandwidth during 48h, 90%cpu...), and it's very annoying. That's why I posted the following bug report,
Archive "back" links dangerous for spiders and robots.
I just came accross a suggestion for that (apparently dead) archive module, in the following node :
Replace core archive.module w/ codemonkeyx archive.module
Will this be fixed in drupal 4.7 ? I think it's better not to include a faulty module (in core !) in a recent stable drupal version. Perhaps that module should be moved out of core and placed in contrib module, to allow users to choose which module they want to use (the new one, or the bad old dangerous one).
What do you think?
Comments
Really the module?
I'm wondering whether it really is the module, or if the database is misbehaving.
Are you running a slow query log to find out? I recommend that you should.
(I'm not arguing that archive.module takes too long to render pages oftentimes. I have it disabled too, but mostly because I think its interface is horrible for users).