XYplorer64 TB v27.90.0020 - Two performance issues

[bobfleming]

Trialling the noinstall version.

1. App consistently takes thirty seconds to start.

2. Navigating to \\wsl.localhost paths takes a similar amount of time. This operation is also not too quick in 27.00.0100.

[admin]

Okay, thanks for the report. As I understand it, TB is still in the beta phase before any optimizations. We have to assume that it will be faster later on.

[Horst]

Trialling the noinstall version.
1. App consistently takes thirty seconds to start.

Not here.
The current version take less than 3 seconds to start.
Your time may come from open tabs with special environment
left open on the last exit.

[admin]

Less than 2 sec for me (but XY-VB is less than 0.8 sec).

This might enlighten: text <get loadtimes>;

[MBaas]

Interesting thread, I'd like to jump in

I looked at the details on my machine and found " 36.957 ms - Load Maxi Tree" - so what does mean and how can I affect that time?

[Horst]

Less than 2 sec for me (but XY-VB is less than 0.8 sec).

This might enlighten: text <get loadtimes>;

Measured
Loaded: 2025-08-07 18:12:10 in 1.587 ms

[admin]

Interesting thread, I'd like to jump in

I looked at the details on my machine and found " 36.957 ms - Load Maxi Tree" - so what does mean and how can I affect that time?

Well, as I said, it's too early to go into it. TB has to come out of the optimization phase first. Anyway, how long does XY-VB take for that same Mini Tree? And try several times always, to benefit from Windows caching and get File I/O out of the equation.

[MBaas]

XY-VB took 17secs, but I'm not sure it's exactly the same (mini or maxi) tree - I haven't used XY-VB for quite some time...

[admin]

I'd say everything over 2 seconds points to some I/O problem that's not directly caused by XY, and most likely it's network related (unless your mini tree is gigantic, which you can also check at the bottom of the load times report).

[MBaas]

Thanks! It's been useful to talk about it - I actually don't use the tree that much, so I've cleared it and total load time is 3.3secs now - much better!