Jocelyn Fournier

FYI Varnish has been running with the original -s malloc,12288m -s static=file,/tmp/varnish_storage.bin,100G and jemalloc 5.3.0 without any issue so far!

Hi @Dridi Just to be sure, release 7.2.1 should be fine for this test, no need to use develop?

Hi @Dridi FYI it's not possible to start varnish with jemalloc 3.6 & the debug config on arm because of the munmap issue: déc. 25 21:42:30 ip-172-29-97-79.eu-west-1.compute.internal varnishd[22282]: Version: varnish-7.2.1...

Hi @Dridi I'm now evaluating the 7.2.1 version compiled without jemalloc (+ varnish-modules) on a arm AWS graviton2 processor (compiled with gcc10 & mcpu=neoverse-n1 flags). I'll let you know if...

Hi @Dridi FYI 7.2.1 without jemalloc using patch from #3881 seems to work pretty well on AWS arm. I see a few spike in CPU usage during aggressive google crawls...

I confirm after more than 1 week of use everything is still really stable on ARM without jemalloc.

ahah, I was expecting this, I've been lazy just fetching upsteam changes :D

There are big drawbacks with this proposed fix: - the whole result will be sent by MySQL to PHP, which will increased a lot the network trafic (and the time...

@Hlavtox It's not the number of product in the category which matters, but the number of lines returned by your query. In your example, how many rows are really returned...

> @jocel1 > > > @Hlavtox It's not the number of product in the category which matters, but the number of lines returned by your query. In your example, how...