This probably applies to more low end devices, but treeherder is basically unusable on Windows on Arm devices (both in IE and Fx). It's super slow to load (maybe minutes?) and even when it does interactions are so delayed it's not really usable.

There are a couple use cases where this matters:

1. As a dev working on WoA support it would be really nice to be able to use treeherder to pull down try builds for testing
2. As a dev testing WoA it would be nice if I could download test packages and look at test logs to pull out relevant command lines
3. As someone not actively writing code it would be nice to use my low end but high battery length WoA device to triage test failures

Hi!

I'm curious to know whether the performance is just as bad on x64 if the CPU is throttled to a similar speed, or if it's architecture specific. eg the JS engine isn't as optimised for ARM. Though if IE is slow too, perhaps it's less likely to be the latter. Btw do you mean IE or Edge? If IE, I would expect performance to be bad + Treeherder doesn't support it in our Babel config etc.

If this ends up being a general "Treeherder is unusable on slower devices", this bug likely overlaps with bug 1499551 / bug 1510280 and other deps of the meta bug 1067846.

Would you be able to experiment with CPU throttling on x64 and see which case it is? :-)

(In reply to Ed Morley [:emorley] from comment #1)

Hi!

I'm curious to know whether the performance is just as bad on x64 if the CPU is throttled to a similar speed, or if it's architecture specific. eg the JS engine isn't as optimised for ARM.

This is definitely true, we have ion disabled for arm64 right now.

Though if IE is slow too, perhaps it's less likely to be the latter. Btw do you mean IE or Edge? If IE, I would expect performance to be bad + Treeherder doesn't support it in our Babel config etc.

Sorry, yes I meant Edge.

If this ends up being a general "Treeherder is unusable on slower devices", this bug likely overlaps with bug 1499551 / bug 1510280 and other deps of the meta bug 1067846.

Would you be able to experiment with CPU throttling on x64 and see which case it is? :-)

I'm not sure a) how to throttle an x86_64 device b) and even if I could I'm not sure what would be a reasonable comparison for this device. It has an 8 core snapdragon 850 clocked at "up to" 2.96 GHz and 8GB of memory, so while it's "low end" it's still somewhat decent specs.

(In reply to Eric Rahm [:erahm] (ni? for phab reviews) from comment #2)

I'm not sure a) how to throttle an x86_64 device

Chrome devtools has a CPU throttle/emulation option iirc.

b) and even if I could I'm not sure what would be a reasonable comparison for this device. It has an 8 core snapdragon 850 clocked at "up to" 2.96 GHz and 8GB of memory, so while it's "low end" it's still somewhat decent specs.

True :-)