# Run a benchmark against an old ES deployment circa 5.6? **URL:** \ **Category:** Elasticsearch\ **Tags:** rally\ **Created:** [July 23, 2022, 2:29pm UTC](https://discuss.elastic.co/t/run-a-benchmark-against-an-old-es-deployment-circa-5-6/310456 "2022-07-23T14:29:22Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![nethlaria](https://avatars.discourse-cdn.com/v4/letter/n/cab0a1/32.png) [@nethlaria](https://discuss.elastic.co/u/nethlaria)\ **Post date:** [July 23, 2022, 2:29pm UTC](https://discuss.elastic.co/t/run-a-benchmark-against-an-old-es-deployment-circa-5-6/310456/1 "2022-07-23T14:29:22Z")
Hi, I'm trying to run some benchmarks for older versions of the service we're running (had some comments from users about "performance not being so good nowadays") and wanted to prove it wasn't the case or find out if there is an issue. I have an instance of it with ES 5.6.16 which I think is as far as it could go along that branch before EOL. Can I check out and compile Rally from an old version and if so, any idea which one is the least old? TIA. ---
**Author:** ![nethlaria](https://avatars.discourse-cdn.com/v4/letter/n/cab0a1/32.png) [@nethlaria](https://discuss.elastic.co/u/nethlaria)\ **Post date:** [July 23, 2022, 2:42pm UTC](https://discuss.elastic.co/t/run-a-benchmark-against-an-old-es-deployment-circa-5-6/310456/2 "2022-07-23T14:42:08Z")
Never mind, v2.1.0 works for that version of ES I think. I installed pyenv and switched to python 3.8 then pip install esrally==2.1.0 did the trick. ---
**Author:** ![Quentin\_Pradet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/quentin_pradet/32/94192_2.png) [@Quentin\_Pradet](https://discuss.elastic.co/u/Quentin_Pradet)\ **Post date:** [July 25, 2022, 9:42am UTC](https://discuss.elastic.co/t/run-a-benchmark-against-an-old-es-deployment-circa-5-6/310456/3 "2022-07-25T09:42:13Z")
Glad that you were able to solve your issue! In the future, note that you can look at the [migration guide](https://esrally.readthedocs.io/en/stable/migrate.html) to see when specific versions of Elasticsearch get dropped. In this case, as you noticed, support was dropped in 2.2.0: [Migration Guide - Rally 2.6.0 documentation](https://esrally.readthedocs.io/en/stable/migrate.html#support-for-elasticsearch-5-x-has-been-dropped), so 2.1.0 is indeed the last version with Elasticsearch 5.x support. Note that if you then want to compare results with a newer version of Elasticsearch, you should use the same version of Rally if possible, as upgrading Rally can potentially give different results: we continually improve it to report more realistic results. ---
**Author:** ![nethlaria](https://avatars.discourse-cdn.com/v4/letter/n/cab0a1/32.png) [@nethlaria](https://discuss.elastic.co/u/nethlaria)\ **Post date:** [July 25, 2022, 10:40am UTC](https://discuss.elastic.co/t/run-a-benchmark-against-an-old-es-deployment-circa-5-6/310456/4 "2022-07-25T10:40:10Z")
Thanks Quentin. Maybe I should start another thread but do you know how to force the elasticsearch client to use requests (as opposed to urllib3)? I am having some SSL configuration problems with the latter but the former seems to work in all cases. I tried passing connection\_class:RequestsHttpConnection as a client option but it doesn't work. ---
**Author:** ![Quentin\_Pradet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/quentin_pradet/32/94192_2.png) [@Quentin\_Pradet](https://discuss.elastic.co/u/Quentin_Pradet)\ **Post date:** [July 25, 2022, 11:53am UTC](https://discuss.elastic.co/t/run-a-benchmark-against-an-old-es-deployment-circa-5-6/310456/5 "2022-07-25T11:53:18Z")
Yes, please open another topic. Rally only supports urllib3, but I'm sure we can help you with the issues you're seeing. ---
**Author:** ![Quentin\_Pradet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/quentin_pradet/32/94192_2.png) [@Quentin\_Pradet](https://discuss.elastic.co/u/Quentin_Pradet)\ **Post date:** [July 25, 2022, 2:01pm UTC](https://discuss.elastic.co/t/run-a-benchmark-against-an-old-es-deployment-circa-5-6/310456/6 "2022-07-25T14:01:26Z")
Looking more closely at the code, there's no reason why requests would not work actually. But we've never tested it. Can you please share in what way it does not work? ---
**Author:** ![nethlaria](https://avatars.discourse-cdn.com/v4/letter/n/cab0a1/32.png) [@nethlaria](https://discuss.elastic.co/u/nethlaria)\ **Post date:** [July 25, 2022, 2:05pm UTC](https://discuss.elastic.co/t/run-a-benchmark-against-an-old-es-deployment-circa-5-6/310456/7 "2022-07-25T14:05:38Z")
You already saw but since it's maybe more a client issue I opened this thread: > [@Elasticsearch6 python client - SSL works with RequestsHttpConnection, but not with Urllib3HttpConnection](https://discuss.elastic.co/t/elasticsearch6-python-client-ssl-works-with-requestshttpconnection-but-not-with-urllib3httpconnection/310541): > > Hi, having a headscratching time trying to use elasticsearch python client with client certs. Using the same client certs (they're definitely fine), I can only connect using the RequestsHttpConnection class. Here's some example code: #! /usr/bin/python3 from elasticsearch6 import Elasticsearch, RequestsHttpConnection, Urllib3HttpConnection client = Elasticsearch(hosts=['https://storage.k8s.myvm:30002'], #k8s node port is \> 30000 verify\_certs = False, ssl\_assert\_hostname = False, ssl\_sh… Thanks ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 22, 2022, 2:06pm UTC](https://discuss.elastic.co/t/run-a-benchmark-against-an-old-es-deployment-circa-5-6/310456/8 "2022-08-22T14:06:20Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.