--
You received this message because you are subscribed to the Google Groups "ngx-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ngx-pagespeed-di...@googlegroups.com.
Visit this group at https://groups.google.com/group/ngx-pagespeed-discuss.
For more options, visit https://groups.google.com/d/optout.
You could consider taking a look at downstream caching:Alternatively, if no html filtering is required, you could experimentingwith switching to OptimizeForBandwidth, and disallowing optimization of all html paths.The html should retain it's original cacheability in this setup.Otto
On Mon, Mar 12, 2018 at 12:34 AM Yaroslav Nakonechnikov <psych...@gmail.com> wrote:
Hello,--i've read old topic, but some things were changed, so...is there any options to increase perfomance?
to check perfomance i'm using ab (apache benchmark).
when i use nginx without pagespeed, i have about 400req/s.when i turn on pagespeed without any filters - i see 80req/s.when i use pagespeed with some filters - same 80req/s.all i want is to use some specific filters with 200-300 req/s... is it possible?my site is based on joomla 3.8, nginx 1.11.9, php7.0, memcached + varnish for additional caching.
You received this message because you are subscribed to the Google Groups "ngx-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ngx-pagespeed-discuss+unsub...@googlegroups.com.
Visit this group at https://groups.google.com/group/ngx-pagespeed-discuss.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "ngx-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ngx-pagespeed-discuss+unsub...@googlegroups.com.