Jason Wilder d54f930c2d Don't parse points twice when receiving remote writes ... The monitoring stats were causing points to be parsed twice create more cpu time just parsing points.		2016-01-27 14:24:56 -07:00
..
internal	Support dropping non-Raft nodes	2015-10-04 00:19:52 -07:00
balancer.go	buildable meta -> services/meta	2016-01-21 15:28:32 -05:00
balancer_test.go	Fix cluster tests	2016-01-21 15:28:34 -05:00
client_pool.go	Use read locks instead of write lock for connection pools checkout	2015-06-08 11:21:07 -06:00
config.go	Use a bounded pool for remote writes	2016-01-26 17:08:36 -07:00
config_test.go	Allow the PointWriter timeout to be configurable	2015-07-02 12:50:12 -04:00
points_writer.go	Use a bounded pool for remote writes	2016-01-26 17:08:36 -07:00
points_writer_test.go	Fix cluster tests	2016-01-21 15:28:34 -05:00
pool.go	Use a bounded pool for remote writes	2016-01-26 17:08:36 -07:00
rpc.go	Use faster point parsing for remote writes	2016-01-27 14:24:09 -07:00
rpc_test.go	Remove ownerID from protobufs	2015-06-02 14:45:52 -06:00
service.go	Don't parse points twice when receiving remote writes	2016-01-27 14:24:56 -07:00
service_test.go	Use a bounded pool for remote writes	2016-01-26 17:08:36 -07:00
shard_mapper.go	Use TCPHost for writing and query to other nodes	2016-01-21 15:28:34 -05:00
shard_mapper_test.go	refactor SelectMapper	2015-09-22 13:09:26 -06:00
shard_writer.go	Use a bounded pool for remote writes	2016-01-26 17:08:36 -07:00
shard_writer_test.go	Use a bounded pool for remote writes	2016-01-26 17:08:36 -07:00