Welcome to the Question2Answer Q&A. There's also a demo if you just want to try it out.
+1 vote
in Q2A Core by
I'm running the following stack:

2-CPU 8-core Intel Xeon CPU, 8GB RAM

Windows Server 2008 R2 64-bit

Apache 2.2.21

MySQL 5.5.29

Php 5.2.17

(if you need any more information let me know)

What happens is that shortly after apache comes online the server response times start out at about 1-2 seconds. Then they quickly (within a few min) rise to 30 - 120 seconds (apache is configured to kill the request after 120 seconds). I've found that stopping and starting apache seems to solve the problem for a few min. However, bouncing apache continually is not a good solution.

The apache error logs seem to indicate that the time is spent in qa-include/qa-db.php. I've checked the queries, and they can be anything from the query that loads the landing page, to a 'show tables;' This leads me to beleive that it's not really the queries, since it seems to stop at a random query, but a general connection problem with MySQL.

To my question, has anyone seen behavior like this before and found a solution?


Q2A version: 1.5.4

Please log in or register to answer this question.