By design, the Drupal CAPTCHA module disables page caching for pages it is enabled on.
So if you enable CAPTCHA for user login and/or registration forms, those pages will not be cached. This is often acceptable.
However, if you enable CAPTCHA for comments, and have the comment form visible at the bottom of each node, then a big portion of your site's pages will not be cached in the page cache at all.
This means that every node will be treated as if the user is logged in, even though it is anonymous visitors who are hitting. This incurs a lot of PHP execution and SQL queries to the database.
So, even though you are using memcache for your page cache, the site would probably suffer.
Adrian (not verified)
Then, how to overcome thisFri, 2011/11/04 - 00:11
Then, how to overcome this issue?
See aboveFri, 2011/11/04 - 11:44
See my "Two options" comment above.
DTI (not verified)
Oh cool. Having justFri, 2011/11/04 - 00:31
Oh cool. Having just received my third "your VPS is over capacity" email in a week, from a client's site with every kind of caching I have access to (including Boost but not memcache) I've been wondering what the heck I've been doing wrong. If this is the reason that could be very cool.
The action to take if you use CAPTCHA (at least for D6) would be to
1) go to admin/content/types
2) Click the edit link for the page, blog entry, or other type you want to modify
3) Scroll down to Comment Settings
4) Find "Location of Comment Submission Form"
5) Select the "Display on separate page" option
6) Click Save Content Type
Repeat for each content type that might be displayed often enough to degrade performance.
Adjust accordingly for D7.
Visitor (not verified)
Not if you cache with Boost.Fri, 2011/11/04 - 01:38
Not if you cache with Boost.
Which means CAPTCHA will not workFri, 2011/11/04 - 11:43
This means that CAPTCHA will not work either.
Boost is not suitable for large sites. Only for smallish sites on shared hosting.
We have an upcoming article on how it can slow down your site more than help it.
dalin (not verified)
This is my experience asFri, 2011/11/04 - 13:57
This is my experience as well. I've done half a dozen performance audits where Boost was causing severe slowdowns on cron and when the node form was saved.
catch (not verified)
Mollom will also do this ifFri, 2011/11/04 - 01:49
Mollom will also do this if you have 'captcha only' on the comment form for any reason.
YesFri, 2011/11/04 - 11:42
Yes, you want it set to text analysis for comments, before it falls back to CAPTCHA.
Michael (not verified)
So, what do you suggest weFri, 2011/11/04 - 06:23
So, what do you suggest we use for preventing spam? Does mollom work for cached pages because it is offsite? I find it good if you tell someone what not to do you should have a solution for what they can.
Two optionsFri, 2011/11/04 - 11:40
1) Make comments on a separate form. See the comment by DTI below for details.
2) Use Mollom, and make sure it is set as follows:
Protection mode: Text analysis
When text analysis identifies spam: Automatically discard the post