"tree" is ~4x times faster than "eza --tree" about eza HOT 1 OPEN

For me
eza --treeis 11.41s
tree 1.08s + ~1s of terminal rendering (which is slower for tree)
One observable difference, the tree command doesn't stop before printing,
which leads me to belive, it doesn't build an internal map of the structure of files and folders, I think it prints as it crawls, and it is good at it's job. I think eza takes time to do allocations and remembering what is where before printing, which makes it slower, because it's not just a tree printer, and it reuses (probably) the same code for other file tree things

BTW
25660 directories, 228326 files
so not complaining

from eza.