Closed csdougliss closed 9 years ago
I have similar problem in the past, and the problem was redis session locking, try to disable it - if you are using module Cm_Redis_Session.
@b3k No change I'm afraid!
I think what @b3k mentioned is what happens with the included default config if you have the crawler-session code enabled, as Gatling would most likely always get the frontend=crawler-session
code, which does not apply in your case @craigcarnell . Looking at your code, it should work fine though, I don't see any obvious problems...
try fix suggested here. https://github.com/nexcess/magento-turpentine/issues/470
jharrisonau's fix in #470 fixes this problem.
This seems to be fixed by #470, closing the issue.
Hi,
I have a store that is running amazingly fast (thanks to turpentine etc) for single users. But when I hit with say Gatling and 200 users concurrently it grinds to a halt.
The setup is Varnish Cache 4.0.1 with Nginx + HHVM + Redis Cache + Redis Session. Server setup is 32 cores, 120gb of RAM, 40 GB SSD.
Gatling
Varnish
/etc/varnish/default.vcl
nginx 1.6.2 - nginx.conf
nginx site.conf
hhvm
/etc/sysctl.conf
/etc/security/limits.conf
ulimit -a