streaming processing and series limiting on other cluster calls

[Dieterbe]

#1021 introduced streaming processing and series limiting for clusterFindByTag

findSeries (which does a similar thing but for non-tagged queries) should get the same changes.

we should probably also switch these to stream processing:
clusterTagDetails, clusterTags, clusterAutoCompleteTags, clusterAutoCompleteTagValues

@shanson7 @woodsaj not sure if my memory is failing me, but i just realized spec-exec is implented for all the above calls, but not for actually getting data (getTargets). what's the reasoning for this? have we discussed this before? seems we should also switch this over to peerQuerySpeculativeChan

[Dieterbe]

eventually we should be able to delete peerQuerySpeculative and just use peerQuerySpeculativeChan

[shanson7]

I believe the reason we don't do speculative execution for getTargets is that those requests target a subset of peers (just the ones that had matching series) and each peer gets a different request.

It could still do speculative execution, it would just look a bit different and might be harder to pick a threshold, since a variable number of peers are involved.

[woodsaj]

I think #1104 is relevant to this discussion

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.