microsoft
Liveshare slow down the whole PC by saturating SSD query queue.
Describe what happened:
What was your system configuration? Product and Version [VS/VSCode]: VS 16.9.5 OS Version[macOS/Windows]: Live Share Extension Version: 1.0.3587.1 Target Platform or Language [e.g. Node.js]: C# Steps to Reproduce / Scenario:
- Run LiveShare
- Someone join the session.
Now you can witness SSD high usage (but the bandwidth usage is really low, below 1Mo/s)
Now procmon show that something is happening:
Liveshare logs to a file, and almost flush for every log line (1.3 log per flush~).
The logfile being written: 20210515_145034_Agent.log
It looks like liveshare logs a lot, and because Trace.AutoFlush is set to true, each logged line causes a flush to the logfile.
Thanks for the report @Kuinox . I think you're right that our logs are too verbose and we may flush too often. Let me look into making the default log level less verbose and reducing how often we flush.
Hello ! Is this issue still considered ? Is there any way we can help on this issue ? My team is using Liveshare on a daily basis to do mob programming with 4 developers connected. VS Code becomes really unresponsive since a few month ago during our coding sessions 😟
Hey @abalhier, we're currently working on it and should have something that'll help in the next release or so.
Hey @abalhier, we're currently working on it and should have something that'll help in the next release or so.
Still working on it?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically in 2 days.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
We’re not able to prioritize this issue over the other higher-impact issues we receive every week, based on the votes and comments from others in the community and our understanding of the issue. We understand this may be disappointing; we've all been there, whether in this project or others we've contributed to. However, rest assured that we love your input. If you feel it deserves to stay open, then clarify your use case and contact us to let us know how severe it’s for you.
