openstack/deb-python-cassandra-driver
Code Issues Proposed changes

For callback chaining, use old pattern of no-timeouts

Browse Source 
Avoids the overhead of timer management when using the callback chaining
pattern.
This commit is contained in:
Adam Holmberg
2015-06-19 13:01:10 -05:00
parent ee2243c217
commit f779da72d8
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
benchmarks/callback_full_pipeline.py
View File

@@ -42,7 +42,7 @@ class Runner(BenchmarkThread):
self.event.set()
if next(self.num_started) <= self.num_queries:
future = self.session.execute_async(self.query, self.values)
future = self.session.execute_async(self.query, self.values, timeout=None)
future.add_callbacks(self.insert_next, self.insert_next)
def run(self):

4
cassandra/concurrent.py
View File

@@ -138,7 +138,7 @@ def _handle_error(error, result_index, event, session, statements, results,
return
try:
future = session.execute_async(statement, params)
future = session.execute_async(statement, params, timeout=None)
args = (next_index, event, session, statements, results, future, num_finished, to_execute, first_error)
future.add_callbacks(
callback=_execute_next, callback_args=args,
@@ -176,7 +176,7 @@ def _execute_next(result, result_index, event, session, statements, results,
return
try:
future = session.execute_async(statement, params)
future = session.execute_async(statement, params, timeout=None)
args = (next_index, event, session, statements, results, future, num_finished, to_execute, first_error)
future.add_callbacks(
callback=_execute_next, callback_args=args,