{"push_id":1001092043,"size":1,"distinct_size":1,"ref":"refs/heads/scan-chunk-2","head":"2b0cc3f344034ee2e34d26e2e349dce64518d239","before":"81a11ace287adce3a5da32eb9831307d28e414d6","commits":[{"sha":"2b0cc3f344034ee2e34d26e2e349dce64518d239","author":{"email":"ec1657b07dda0ff6262dc7efd2e7e3cc188a9ea2@gmail.com","name":"Radu Berinde"},"message":"sql: break up single-span scans into chunks\n\nIn this change we break up table scans into chunks (#2966), but only when we\nhave a single span. We need to improve the KV API to provide a per-batch limit\nwhen we have multiple spans (tracked by #4696).\n\nThis change will also automatically improve the LIMIT cases like the example\nin #4299.\n\nOn a single node, 1,000 keys was enough to not cause performance degradation\n(see below). On actual clusters we likely need bigger chunks to hide the higher\nlatencies; setting at 10,000 for now.\n```\nname \\ time/op         bench-100    bench-500    bench-1000   bench-5000 bench-10000  bench-inf\nScan10000_Cockroach-4  82.5ms ±15%  42.9ms ± 4%  37.0ms ±12%  41.4ms ±46% 35.8ms ±17%  35.3ms ± 7%\n```","distinct":true,"url":"https://api.github.com/repos/RaduBerinde/cockroach/commits/2b0cc3f344034ee2e34d26e2e349dce64518d239"}]}