Currently each write is flushed, and so the number of result events triggered are numerous. This affects the responsivenes of neovim greatly when running the entire test suite on large projects. Using the :delayed_write option (doc) improves this greatly.
Obviously with streaming this will reduce the live update a bit, but it's not very noticeable IMO.
The size and delay values are configurable. Sticking to default right now (as per docs it's 64kb, 2 seconds)
Currently each write is flushed, and so the number of result events triggered are numerous. This affects the responsivenes of neovim greatly when running the entire test suite on large projects. Using the
:delayed_write
option (doc) improves this greatly. Obviously with streaming this will reduce the live update a bit, but it's not very noticeable IMO. Thesize
anddelay
values are configurable. Sticking to default right now (as per docs it's 64kb, 2 seconds)Before the change
After the change