The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
RamiusJoined: July 19, 2000Administrator, ClubPAadmin
edited December 2007
yeah, me too. I'm not sure the cause, yet. Our load average on the webservers is fine. I don't have management or observational capabilities for the database server, but I would guess that is where we are timing out. That box is shared amongst many parts of the site, and so it is possible there is something going on elsewhere (store, mainsite, adverts, etc) which is affecting us, here.
RamiusJoined: July 19, 2000Administrator, ClubPAadmin
edited December 2007
yeah, that would be a "soft" timeout. The 504 gateway timeout is basically the reverse proxy reporting that it has given up waiting for Apache to respond. But you can have a timeout that takes several seconds before the proxy gives up, which eventually results in a successful pageload.
I seem to get them every time I try to post. In G&T at least, hopefully this gets through here.
edit- Ah yes, it does about half an hour later. I'm guessing you guys already know how broken the forums were for about an hour there and this would be why it's fixed.
edit- Yikes! Multipost a palooza! Seems they all eventually got through after all.
Haven't had a problem for a while now, but just this evening I've had a couple of instances of slow loading, and a 504 Gateway Time-Out. This isn't bitching about problems or anything like that, just checking if it's an issue that's still around/coming back.
darleysam on
0
RamiusJoined: July 19, 2000Administrator, ClubPAadmin
edited January 2008
Yeah, it is still with us for a little bit, yet.
I have an archiving system on-deck, but an upcoming family vacation will probably push it back yet another couple weeks. There has also been some discussion of dedicating a slave database for searches (which is the main culprit for the timeouts), and even possibly offloading the searches to a search system instead of relying on MySQL's fulltext index. Because of the nature of these changes, I cannot just drop them into the source code and off we go. All of this work requires some reconfiguration of services on the servers and/or installation of new software. So I need to coordinate the work with the overall server maintenance and growth plans, which makes it a little more time-consuming to come to resolution. But Soon! Within the month of January, I'm quite certain, we should see major (and hopefully long-lasting) performance improvements.
Posts
I've been hitting 504s out the ass.
edit- Ah yes, it does about half an hour later. I'm guessing you guys already know how broken the forums were for about an hour there and this would be why it's fixed.
edit- Yikes! Multipost a palooza! Seems they all eventually got through after all.
I have an archiving system on-deck, but an upcoming family vacation will probably push it back yet another couple weeks. There has also been some discussion of dedicating a slave database for searches (which is the main culprit for the timeouts), and even possibly offloading the searches to a search system instead of relying on MySQL's fulltext index. Because of the nature of these changes, I cannot just drop them into the source code and off we go. All of this work requires some reconfiguration of services on the servers and/or installation of new software. So I need to coordinate the work with the overall server maintenance and growth plans, which makes it a little more time-consuming to come to resolution. But Soon! Within the month of January, I'm quite certain, we should see major (and hopefully long-lasting) performance improvements.