-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Tab completion in large folders is very slow #4797
Copy link
Copy link
Closed
Labels
HacktoberfestPotential candidate to participate in HacktoberfestPotential candidate to participate in HacktoberfestResolution-FixedThe issue is fixed.The issue is fixed.Usability(LEGACY) Helps filter issues that might be higher priority because they directly affect usability(LEGACY) Helps filter issues that might be higher priority because they directly affect usabilityWG-Engine-Performancecore PowerShell engine, interpreter, and runtime performancecore PowerShell engine, interpreter, and runtime performanceWG-Interactive-IntelliSensetab completiontab completion
Description
Metadata
Metadata
Assignees
Labels
HacktoberfestPotential candidate to participate in HacktoberfestPotential candidate to participate in HacktoberfestResolution-FixedThe issue is fixed.The issue is fixed.Usability(LEGACY) Helps filter issues that might be higher priority because they directly affect usability(LEGACY) Helps filter issues that might be higher priority because they directly affect usabilityWG-Engine-Performancecore PowerShell engine, interpreter, and runtime performancecore PowerShell engine, interpreter, and runtime performanceWG-Interactive-IntelliSensetab completiontab completion
Steps to reproduce
Get a folder with a decent number of files (65k will do)
Try to do autocompletion on file name in this folder
Expected behavior
Respond time comparable with bash completion (about a second)
Actual behavior
No response for 12 seconds (appears like a hang)
For comparisons,
ls | measurein the same folder takes about 4 seconds (3 times faster), which hints that there is a room for improvements even without a big rewrite for the completion logic.Environment data