So, just what query or page in the survey module do you say was
causing the trouble? This might be quite easy to track down if you
have the Developer Support package installed and turned on.
As it stands, you've basically said "something somewhere in the survey
package sometimes takes a lot more CPU than I think it should", which
is not especially useful as bug report.
