-
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
ble.sh:Perf: menu-complete chokes on directory with 6k+ files #11
Comments
I'm interested in this issue. May I ask what is your operating system, ble.sh version and Bash version? This must be a general performance issue of ble.sh which is written in Bash script, but if I can identify the bottleneck maybe I can improve the performance. If you are using ble-0.3, I recommend you switch to the devel version ( I now have tried 10k files in a directory with the latest version of ble.sh and bash-4.4, 5.0, and 5.1 in Linux. In my environment, it seems to take about 15s to display the menu when |
I haven't check much details, maybe later once I got more info I'll file an issue to the main ble.sh repo.
Yes, I can reproduce this multiple times now. Not sure how I got ~30s last time, maybe one of those rare case, or I didn't check the clock properly. Version info: $ echo $BLE_VERSION
0.4.0-devel3+a6b4e2c
$ echo $BASH_VERSION
4.2.46(2)-release
$ lsb_release -a
# RHEL 7.9 |
OK! Thank you! |
I have investigated the bottleneck in the directory with many files. It turned out that there are several reasons that make the menu completion slow. The fixes and workarounds for some bottlenecks are in the mater branch of 1. Delayed initialization for menu items did not work (~ 8 secs)[Fixed]I have fixed it in commit akinomyoga/ble.sh@acc9661. 2. Old
|
This is very good findings! I will duplicate this to ble.sh repo for documentation purposes. |
OK! Thanks! |
In vanilla bash, it will warn user for many files:
Takes ble.sh ~30s to display files in menu-complete. Investigate further.
The text was updated successfully, but these errors were encountered: