Page 1 of 1

Time to first byte problem

Posted: Sat Aug 03, 2013 8:40 pm
by madfish
Hello,

I have a problem with time to first byte on ALL pages. I have disabled product/category count but the problem still persist. Any suggestions ? I will appreciate any help.

http://test.profumino.it

oc. 1.5.5.1

Re: Time to first byte problem

Posted: Sun Aug 04, 2013 2:58 am
by madfish
Is there a possibility to know which call is causing this delay ??

Re: Time to first byte problem

Posted: Sun Aug 04, 2013 6:13 am
by rph
There's a vQmod script for logging database query times from qphoria. Search the forum and you should find it. I believe it will need some adjustment for 1.5.5.1. You can also try upgrading to the most recent version of vQmod. It has speed improvements, especially over older versions.

Re: Time to first byte problem

Posted: Sun Aug 04, 2013 6:37 am
by madfish
I don't know it kind of strange. I upgraded to the last vqmod, but still no improvements. It seems that the first bytes need some time.
I have the same site on 1.5.1.3 with different template and works great.

Re: Time to first byte problem

Posted: Sun Aug 04, 2013 11:30 am
by rph
If you're using webpagetest.org keep in mind that it will fail you on TTFB even when you might have made a big improvement. I've seen upgrading vQmod decrease TTFB by 0.4 seconds which is substantial but the site still failed because TTFB was 2 seconds.

I'd start by testing TTFB on a static page on your server. If the issue persists the problem is the server or network setup. If it goes away you'll need to methodically step through different possible bottlenecks.

Re: Time to first byte problem

Posted: Sun Aug 04, 2013 6:11 pm
by madfish
As I said I have the same site on the same server : profumino.it , which has a first time to byte like 0,5seconds or so... meanwhile this newer site test.profumino.it has a 4 seconds - and also it feels like a lag when browsing.

Re: Time to first byte problem

Posted: Sun Aug 04, 2013 8:02 pm
by madfish
Ok I got it ... it's product_to_category database with MORE THAN 65.000 entries. If anyone know any fix for that I would be more than happy to listen.