Answers.Body: <p>If I'm looking at the right site, it looks like the second page of your event registration has a consistent 60 second delay added on top of the usual page generation times, and that the delay is introduced before the user is asked for payment.</p>
  
  <p>Unless your payment processor requires communication before the transaction, this suggests that the issue is within CiviCRM or your hosting environment.</p>
  
  <p><strong>An additional 60 or 120 second delay is often a timeout</strong>, for example when a webserver attempts to get reverse DNS during the request and fails. However there's no way to be sure without looking under the hood, so I'll provide general advice on how to proceed also :)</p>
  
  <ul>
  <li>Use tools like <a href="http://www.webpagetest.org">http://www.webpagetest.org</a> or <a href="http://fpt.pingdom.com">http://fpt.pingdom.com</a> to ensure your site performs well generally - enter the URL of your registration pages and make sure <em>the entire page</em> is delivered to the visitor within a few seconds.</li>
  <li>Ensure your hosting environment is capable of delivering your content in a reasonable timeframe.</li>
  <li>Disable configurations which add to request time, eg reverse DNS lookups.</li>
  </ul>
  
  <p>I suspect this issue is not related to your payment processor at all.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-28T13:59:12.160Z
Answers.Text: Pingdom and webpagetest.org show the site is good overall. Hosting environment is a managed cloud server from Rochen, and is doing well. We have a dedicated MySQL db server as well, which is running good also. I haven't looked into reverse DNS lookups.
Answers.UserDisplayName: globalawakening
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-28T19:46:11.803Z
Answers.Text: If you have a separate DB server, you may see DNS issues between webserver and DB server also. Make sure both servers recognise all hostnames used in communication (caching DNS or /etc/hosts entries). Note that rDNS is only one possible cause of this behaviour - but I've seen it happen plenty, and it's frequently a source of confusion because it's not obvious.
Answers.UserDisplayName: Chris Burgess
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-28T19:47:27.620Z
Answers.Text: I think your next step is to contact your developers and have them investigate the issue. If it's reproducible, it should be straightforward for a developer with access to the system to identify and eliminate.
Answers.UserDisplayName: Chris Burgess
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-27T22:12:47.070Z
Answers.LastActivityDate: 2015-05-27T22:12:47.070Z
Answers.UserDisplayName: Chris Burgess
Body: <p>On events which require payment, the system takes up to 2 minutes to generate the second page of the registration process, which is the page titled "Confirm Your Registration Information".</p>
  
  <p>What is the problem, and what can I do to bring the performance up to acceptable levels?</p>
  
  <p>The site runs quickly on every other page, including other CiviCRM tasks. It is only this process which is slow.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-05-27T21:08:02.883Z
Comments.Text: whats your payment processor? Can you do a test run and use the dummy payment processor and see if it is still slow
Comments.UserDisplayName: Donald Lobo
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-05-27T21:22:11.477Z
Comments.Text: Do other CiviCRM functions run more quickly, or is it potentially a server resources issue? What kind of a server are you running on?
Comments.UserDisplayName: Laryn
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-05-28T13:53:21.320Z
Comments.Text: Yes, everything else seems to run quickly. The site runs smooth across the board. I have all caching disabled, but it's still loading quickly, except for this page.
Comments.UserDisplayName: globalawakening
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-05-28T14:05:42.933Z
Comments.Text: Payment processor is Authorize.net
Comments.UserDisplayName: globalawakening
Tags: <civievent><payment-processor>
Title: System Slow - Event Registration with Payment
ThreadText: # System Slow - Event Registration with Payment
  
  (Asked by: username_0 on 2015-05-27)
  
  On events which require payment, the system takes up to 2 minutes to generate the second page of the registration process, which is the page titled "Confirm Your Registration Information".
  
  What is the problem, and what can I do to bring the performance up to acceptable levels?
  
  The site runs quickly on every other page, including other CiviCRM tasks. It is only this process which is slow.
  
  **Tags:** civievent, payment-processor
  
  > **Comments:**
  > **username_1**: whats your payment processor? Can you do a test run and use the dummy payment processor and see if it is still slow  
  > **username_2**: Do other CiviCRM functions run more quickly, or is it potentially a server resources issue? What kind of a server are you running on?  
  > **username_0**: Yes, everything else seems to run quickly. The site runs smooth across the board. I have all caching disabled, but it's still loading quickly, except for this page.  
  > **username_0**: Payment processor is Authorize.net  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_3 on 2015-05-27. Score: 5
  
  If I'm looking at the right site, it looks like the second page of your event registration has a consistent 60 second delay added on top of the usual page generation times, and that the delay is introduced before the user is asked for payment.
  
  Unless your payment processor requires communication before the transaction, this suggests that the issue is within CiviCRM or your hosting environment.
  
  **An additional 60 or 120 second delay is often a timeout**, for example when a webserver attempts to get reverse DNS during the request and fails. However there's no way to be sure without looking under the hood, so I'll provide general advice on how to proceed also :)
  
  * Use tools like <http://www.webpagetest.org> or <http://fpt.pingdom.com> to ensure your site performs well generally - enter the URL of your registration pages and make sure *the entire page* is delivered to the visitor within a few seconds.
  * Ensure your hosting environment is capable of delivering your content in a reasonable timeframe.
  * Disable configurations which add to request time, eg reverse DNS lookups.
  
  I suspect this issue is not related to your payment processor at all.
  
  > **Comments:**
  > **username_0**: Pingdom and webpagetest.org show the site is good overall. Hosting environment is a managed cloud server from Rochen, and is doing well. We have a dedicated MySQL db server as well, which is running good also. I haven't looked into reverse DNS lookups.  
  > **username_3**: If you have a separate DB server, you may see DNS issues between webserver and DB server also. Make sure both servers recognise all hostnames used in communication (caching DNS or /etc/hosts entries). Note that rDNS is only one possible cause of this behaviour - but I've seen it happen plenty, and it's frequently a source of confusion because it's not obvious.  
  > **username_3**: I think your next step is to contact your developers and have them investigate the issue. If it's reproducible, it should be straightforward for a developer with access to the system to identify and eliminate.  
  
  ---
  
  