Open benweissmann opened 6 years ago
We can use a technique like https://golang.org/doc/effective_go.html#leaky_buffer instead of allocating a new redisPub for each oplog message. Need to benchmark to determine the actual performance improvement.
redisPub
See: https://github.com/tulip/oplogtoredis/blob/85ebc4bca6b50f572160cdba078c910ebdd89c0b/main.go#L39
We can use a technique like https://golang.org/doc/effective_go.html#leaky_buffer instead of allocating a new
redisPubfor each oplog message. Need to benchmark to determine the actual performance improvement.See: https://github.com/tulip/oplogtoredis/blob/85ebc4bca6b50f572160cdba078c910ebdd89c0b/main.go#L39