thank you for your answers. We double checked and here is my revisited answer:
- you are correct, the
analytics_config.typecannot haveredisvalue. That was a copy/paste issue from our side. - it is also correct that both
enable_analyticsandenable_health_checksconfiguration values work as expected, so if we set them tofalsethey will switch off the corresponding feature. - the root cause of the misunderstanding was that we played with setting them on and off in parallel and mistakenly we came to the conclusion that the
zrangecommand (which takes a lot of time as we measured) is executed by the analytics module.
So, to summarize: after we set the enable_health_checks to false there was a considerable speed increase in Tyk. Basically we came to a very similar conclusion as this thread: Scaling Redis for Tyk in AWS - #5 by kalpik
Thank you for your inputs and for driving me in the good direction.
Jozsef