Voting starts in March for the Drupal Association Board election.
Hi - I actually got this going and it does in fact work. Both Authenticated and unauthenticated user blocks are being cached and the page is being built quite nicely.
My question: The benchmarks are quite counter-intuitive.
The results below are with 25 samples of a content-type page using jmeter. They're part of a process of before and after login looking at the same page. I did a drush cc all and a
varnishadm -S /etc/varnish/secret -T 127.0.0.1:6082 url.purge . between runs (25 login sequences in each run)
Page caching = normal
Page compression = disabled
Block cache = disabled
CSS/JS aggregation = on
|User type||With varnish and ESI||Varnish only||No varnish|
So basically, ESI seems to make the page about 1/4 as fast. What's up with that?
Has anyone else done benchmarking of this?
The poor results with ESI turned on are the same as my experience using a browser. The blocks fill in quickly and then the content comes, and it generally feels slower than the normal.
I would appreciate suggestions of what I could do better in the configuration or benchmarking process. I've attached my vcl files.
I am admittedly a newbie to both varnish and ESI, so I take these results with a grain of salt.