CWPpro Reviews

Started by monkeyking, June 19, 2018, 02:51:55 AM

Previous topic - Next topic

johnny09

Updates on automatic - I run centos 6, you run centos 7

johnny09

How to increase Vanish performance?

monkeyking

You are right I am on Centos 7. I just increase my memory to 4096. But I don't see any improvement in performance. I think that's it. That's all you can push for performance. I guess anything else will depend on hardware.

bullten

#18
It will never optimize your website unless you create varnish rules for your software/website. So moving to hdd or ram allocation wont help unless you follow varnish rules.

Like if you are running wordpress you can search github for premade vcl and use it for your website

Quotehttps://github.com/search?q=varnish+wordpress

monkeyking

Quote from: bullten on June 29, 2018, 04:26:02 PM
It will never optimize your website unless you create varnish rules for your software/website. So moving to hdd or ram allocation wont help unless you follow varnish rules.

Like if you are running wordpress you can search github for premade vcl and use it for your website

Quotehttps://github.com/search?q=varnish+wordpress

Just great, now I am even more confused.

monkeyking

Quote from: bullten on June 29, 2018, 04:26:02 PM
It will never optimize your website unless you create varnish rules for your software/website. So moving to hdd or ram allocation wont help unless you follow varnish rules.

Like if you are running wordpress you can search github for premade vcl and use it for your website

Quotehttps://github.com/search?q=varnish+wordpress

Big thank you. I follow those guides and I noticed that Varnish is working properly now. I used to see Age=0 when I ran tests with tools like pingdom. On second run then I see Age like 10 or so or some other numbers. Then it would dropped back to 0 every so often. Now Age always equal to some numbers. My first test run is almost always as good as second run.

Also, I had issues with "Reduce server response time". I did a lot of homework on this too. And found out that Cloudflare was the cause. They have issues with TTFB (time to first byte). They wrote about it here. https://blog.cloudflare.com/ttfb-time-to-first-byte-considered-meaningles/

I hope that help.