Elasticsearch transport client spawning a large number of threads

Thank you a lot @jprante! We are looking into what is the bottle neck. So far the ad-hoc hot_thread analysis shows that getting term_vectors (which we need for some computations) is taking around 50-60% of actual time ES is working. We are keeping only term frequencies. Do you know if there is a more efficient way to save/retrieve term vectors then default es way?

Thank you again.