How can I manually select to use local instead of server analysis? • page 2/2 • Lichess Feedback • lichess.org

I think the hypothesis of op was that the local engine bundle wasm or whatever nowadays might not exist for both types of CPUs brands. I agree it would explain the difference on test positoin being exactly the same in both machine, in spite of being a waste of resources if being used systematically on every position. But that might have been to show that it was not position dependent.. and might correlate with CPU brand from user experience.. but it might also just be 2 computers of same brand and different computer trajectories... (or user experience on both).

when in doubt reboot, or clear all caches. as site data.. for cleaner testing at least. (the reboot is kidding).

I think the hypothesis of op was that the local engine bundle wasm or whatever nowadays might not exist for both types of CPUs brands. I agree it would explain the difference on test positoin being exactly the same in both machine, in spite of being a waste of resources if being used systematically on every position. But that might have been to show that it was not position dependent.. and might correlate with CPU brand from user experience.. but it might also just be 2 computers of same brand and different computer trajectories... (or user experience on both). when in doubt reboot, or clear all caches. as site data.. for cleaner testing at least. (the reboot is kidding).

Cheshire_the_Maomao edited

#12

@schlawg said in #10:

clear your site data

Thank you! This magically works. Now I reloaded the 79MB SF17 engine and it can work locally. Meanwhile, I no longer can do any more cloud analysis.,

It is really strange. Isn't there an option button to manually alter from local analysis calculation and cloud analysis calculation?

@dboing said in #11:

I think the hypothesis of op was that the local engine bundle wasm or whatever nowadays might not exist for both types of CPUs brands. I agree it would explain the difference on test positoin being exactly the same in both machine, in spite of being a waste of resources if being used systematically on every position.

Sorry I don't understand what you mean. Do you mean I once loaded a wrong WASM figure, and it didn't work on my PC, so Lichess auto chose online cloud analysis for me?

Still, do you think manually alter them? I want to use online analysis when my laptop is on its battery in order to reduce battery usage, and use local analysis when I have a power source.

@schlawg said in #10: > clear your site data Thank you! This magically works. Now I reloaded the 79MB SF17 engine and it can work locally. Meanwhile, I no longer can do any more cloud analysis., It is really strange. Isn't there an option button to manually alter from local analysis calculation and cloud analysis calculation? @dboing said in #11: > I think the hypothesis of op was that the local engine bundle wasm or whatever nowadays might not exist for both types of CPUs brands. I agree it would explain the difference on test positoin being exactly the same in both machine, in spite of being a waste of resources if being used systematically on every position. Sorry I don't understand what you mean. Do you mean I once loaded a wrong WASM figure, and it didn't work on my PC, so Lichess auto chose online cloud analysis for me? Still, do you think manually alter them? I want to use online analysis when my laptop is on its battery in order to reduce battery usage, and use local analysis when I have a power source.

dboing

#13

well I thought the hypothesis of the CPU brand being a factor was that there was not local executable. I just remembered it was using wasm at a time. .not really important. I was just saying it might be plausible hypothesis that the executable might have need to be targetting the CPU brand. although now thinking about it I think that is internal to browwer "web OS" instuction set.

I know very little of web tech.. just making hypotheses.. You should listen to @schlawg more than me.

well I thought the hypothesis of the CPU brand being a factor was that there was not local executable. I just remembered it was using wasm at a time. .not really important. I was just saying it might be plausible hypothesis that the executable might have need to be targetting the CPU brand. although now thinking about it I think that is internal to browwer "web OS" instuction set. I know very little of web tech.. just making hypotheses.. You should listen to @schlawg more than me.