-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changing File type is not responsive - p1 #33
Comments
I'm just seeing this one now. Apparently I never got a notification! I should be able to take a look at this today... We certainly shouldn't be seeing these kinds of performance issues. |
Any chance you could get this into a test case so that I can throw CI at it on various platforms? I'm unable to reproduce it on any of my local machines here. What JVM is showing this behaviour? |
Probably not until September.
$ java -version
openjdk version "16.0.1" 2021-04-20
OpenJDK Runtime Environment (build 16.0.1+9)
OpenJDK 64-Bit Server VM (build 16.0.1+9, mixed mode, sharing) https://bell-sw.com/pages/downloads/#/java-16-current Running on Linux.
Correction: There is a super-slight delay when scrolling/jumping to the end of the listing in the previous release, but not nearly as noticeable as the latest version. |
Ok, that's not a problem. Whenever you can get to it! Looks like I'm still on at most JDK 15. Using the new glob-based filters will be potentially more I/O heavy because they have to ask the filesystem to create new glob matchers, and they have to check Is this exclusive to the new glob filters? |
Seems likely, given that that's the new feature I tried to use, but cannot say with 100% certainty. |
I've never been able to reproduce this, and the OP is gone! |
Replicate:
**/.*
.Expected:
Actual:
Any ideas what's causing these delays? (If it was 10,000 files, I could understand a teeny tiny delay, but using a 3GHz processor alongside 32GB RAM reading from a super-fast SSD, I'd anticipate nearly instantaneous response times even for 10k files, much less ~50.)
The previous version does not exhibit such behaviour. It seems likely that the filters are causing the issues.
See #32 for a minimal example.
The text was updated successfully, but these errors were encountered: