![]() ![]() I am grateful to the community’s contributions and I will happily support/test/integrate any improvements, such as the upcoming Ctrl-Click functionality that was contributed by Fabrizio Iannetti and will be available in Eclipse IDE 2021-06.īecause much of the performance slowdown is because of ConPTY itself, which is actively being developed at Microsoft I hope that Eclipse will benefit from those performance improvements over time. Therefore I plan to focus my time on other areas of the terminal, like WSL integration and bug fixes with larger impacts. I am pleased that the performance of ConPTY with JNA is close to the new dedicated Microsoft Terminal and much faster than VSCode. The code could probably be revisited because presumably the new ConPTY does not suffer from these buffering issues, and the throttling probably should not be there for non-Windows at all. However the terminal has an artificial throttle in this path that limits performance to around 0.01 MiB/s, plenty fast to type, but much slower than a performant system could be. I was going to run an Eclipse -> Shell test to make sure writes to the terminal hadn’t regressed. The above shows that the raw speed of Eclipse Terminal is very good, it simply requires the best possible PTY layer to achieve the best speeds. VSCode is dramatically slower than the rest.įull table of results based on a 10MiB write, reported in MiB/second, rounded to nearest 0.1 MiB/s:Īs a comparison, on the same machine dual-booted into Xubuntu 18.04 I ran the following 5 terminals: ConPTY is quite a bit slower, whether used in Eclipse or Windows Terminal. Short summary is that WinPTY and Windows Command are much faster than the rest.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |