According to jamesh, all the rows are buffered by the postgresql python driver anyway, so getting rows from the resultset, even incrementally, is basically a no-op. That said, we could certainly do this to free up some resources when CPU time is the issue.
The right place to do this check is in the storm TimeoutTracer though, so I'm going to a) downgrade to low because of the minimal benefits, and b) retarget this to storm.
According to jamesh, all the rows are buffered by the postgresql python driver anyway, so getting rows from the resultset, even incrementally, is basically a no-op. That said, we could certainly do this to free up some resources when CPU time is the issue.
The right place to do this check is in the storm TimeoutTracer though, so I'm going to a) downgrade to low because of the minimal benefits, and b) retarget this to storm.