Using eza in large directories

[apcamargo]

A common part of my workflow involves executing ls in large directories (specifically, ls -l large_dir), which prevents me from setting ls as an alias for eza, since eza is significantly slower in large directories compared to ls. This isn't a major issue, and I understand that it's probably not what eza is mainly for. Still, I'm curious if there's any combination of parameters that could make eza run faster when fancy stuff, like Git details, are not really necessary.

[cafkafk]

I just ran eza in a folder with 26218 files and it took an average of 104 miliseconds

  Time (mean ± σ):     103.9 ms ±   1.9 ms    [User: 39.5 ms, System: 64.2 ms]
  Range (min … max):   100.4 ms … 107.9 ms    28 runs

I'm assuming you're running with additional flags. These are likely the reason that your seeing slow speeds. Especially flags like --git-repos will slow down the speed on large dirs, which is why --git-repos-no-status exists, for instance.

[tertsdiepraam]

Actually, this strategy is used already for the extended attributes and absolute path.

[tertsdiepraam]

Sounds like you're volunteering

Happy to if it turns out to be a relatively small fix!

[apcamargo]

Should I open an issue to track this?

[tertsdiepraam]

Good idea! I started this PR once that you could also link to: #833. It was more of an exploration than than a real PR.

[apcamargo]

Done (#922). Sorry that I took so long to do this