Linode Forum
Linode Community Forums
 FAQFAQ    SearchSearch    MembersMembers      Register Register 
 LoginLogin [ Anonymous ] 
Post new topic  Reply to topic
Author Message
PostPosted: Sun Mar 04, 2012 3:45 pm 
Offline
Junior Member

Joined: Sat Jan 07, 2012 4:15 pm
Posts: 23
Hey guys,

I've posted here a few times already - once for this exact issue, and W3C turned out to be the culprit. After implementing the correct server rules, the issue was resolved. Well, as of recently, the site (seemingly sporadically) reflects an extremely slow (4-8 secs) TTFB as evidenced by observation as well as testing it with a service like http://www.webpagetest.org

Now, it isn't consistent, which is good and bad. Usually I observe it when I haven't visited the site for some time (12+ hours?), which made me suspect that it was W3C again. I checked it out, and the W3C config seems correct and the server response headers sane. Of course, this could be being caused by one of the many plugins my client has installed since, but I wanted to get your guys' opinion first before settling on that as the cause.

The site is http://bladereviews.com/

Thanks fellas,
rawsted


Top
   
 Post subject:
PostPosted: Sun Mar 04, 2012 4:39 pm 
Offline
Senior Member
User avatar

Joined: Sat Aug 30, 2008 1:55 pm
Posts: 1739
Location: Rochester, New York
If you take a look at the source code, it appears it's spitting out a buttload of debugging information. This probably isn't helping it.

_________________
Code:
/* TODO: need to add signature to posts */


Top
   
 Post subject:
PostPosted: Sun Mar 04, 2012 4:47 pm 
Offline
Junior Member

Joined: Sat Jan 07, 2012 4:15 pm
Posts: 23
hoopycat wrote:
If you take a look at the source code, it appears it's spitting out a buttload of debugging information. This probably isn't helping it.

I enabled that to try and track down the cause of some minify errors. The issue was present prior to that.

Edit:
For clarification, I think it has something to do with W3TC not writing /wp-content/w3tc/min/default.include.js and default.include.css

It's not a permissions issue (I su'd to the webserver user and was able to create both files in console), but the debug output says:

Bad file param format: "default.include.js"

Googling that turns up all kinds of stuff, from bugs in W3TC to issues with gzip. I disabled gzip and that didn't seem to do anything.

Although, I also disabled minify entirely (I think), and the issue remained, so perhaps it's something more fundamental? It's odd because on subsequent pageviews, everything is normal (fast). It only seems to happen when accessing the index directly.


Top
   
 Post subject:
PostPosted: Wed Mar 07, 2012 9:28 am 
Offline
Junior Member

Joined: Sat Jan 07, 2012 4:15 pm
Posts: 23
I'm still messing with this - could it be caused by keepalive during high traffic times? If that were the case, wouldn't all pages be affected?

I had it set for 10 seconds, then 5, and I just recently brought it down to 1.


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic


Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
RSS

Powered by phpBB® Forum Software © phpBB Group