title: Performance goes bad for range based query on cassandra wide column family when implemented using multithreaded pycassa xget() calls?
body: <p>I have a typical wide column family with {rowkey--> uuid4+date and timeseries data as columns}, on which I have implemented a range based query using pycassa xget() calls. Not that I was plagued with poor performance with single threaded code, I was more like curious to understand the difference in performance when the xget() calls are made in parallel rather than sequential (from inside of a for: loop).</p>
  
  <p>I have used the "threading" python library to implement the multithreaded version of the range based query and performance actually degraded considerably. <strong>Now I am aware of the effect that python GIL has on multithreaded code but is there any way I can be sure that this is infact caused by GIL? Can it be something else that is causing this ?</strong></p>
  
  <p>Thanks in advance. </p>
  
  <p>Note: I am not considering the "multiprocessing" library because I can't afford to have different ConnectionPool object for each sub-process.</p>