Hi! It is hard to answer this question.
Regard Jedis, you don't have any limit in Jedis and it won't become any suboptimal to have a lot of concurrent operations as Jedis just uses a socket per thread. The only limitation there is how many threads your client app can handle.
About Redis. It is also hard to answer. Redis is not multithreaded, which means it can only process one command at a time. So concurrency there us more about avoiding networking waits in my experience.
I had applications that used to send to redis more than 64k commands / second, using Jedis. And you can achieve even more than that.
I don't think this answers your question :)
Jonathan