@ncw can this happen by the failed to wait for in-sequence read issue in this thread?
failed to wait for in-sequence read
after disable the async feature (--async-read=false) it looks much better:
--async-read=false
