Nexcess vs Cloudways (Test 5)
Some additional testing with the porto theme installed.
All tested on the category sample page for Training–>Video Download
Cloudways: varnish, redis not active
Mode: Developer with Porto theme and sample data
Pingdom: 782ms, 80 grade, 1.3MB, 255 requests
Webpagetest: 3.17s, As/b compression, .385TTFB, 1MB 251 requests
Nexcess: redis, no varnish
Mode: Developer with Porto Theme and Sample Data
Pingdom: 73grade, 1.24s, 1.2mb, 255 requests
Webpagetest: As bcompress image, 3.42s, .618TTFB, 251 requests, 1MB
Do Direct installation, no varnish, no redis
Mode: Developer
Pingdom: 656ms, 73 grade, 1.4MB, 259 requests (category page)
Webpage test: A’s b on compress image, 3.864s, .242TTFB, 1MB, 254 requests
All sites were tested on the same test locations and at the same time of day. I tested a couple times each and they stayed consistent. It’s interesting to see the TTFB on DO win by a decent margin, however the overall load time was more. I would imagine that is probably comes to some optimization settings or possibly caching since both nexcess and cloudways either have redis or varnish functional. I have an issue with the porto theme on all the installs and they are looking at the problem. So far they are responsive to this, however I did just buy the theme. Their install and patch system is a bit wonky IMO, but I’m also not in to the development arena, so perhaps what they are doing is standard. Regardless, something isn’t quite right. I get the same issues on 2.3.3 and 2.3.4.
Nexcess is still working on the backup issue. I was hoping they would have had it fixed prior to the weekend so I could do some work. I contacted them in regards to the TTFB on their site as it typically seemed to be around 1s on the stock theme and sample data. They said it was due to DB queries from everyone that was hitting the DB on that specific cloud configuration. IMO, that seems a bit too many people pulling from a single DB instance. He said he would configure a redis setting that should help, however we are holding off on that until they get the backups resolved as I would inevitably just revert the change. Updates to come as I make more progress.