TalkChess.com

It is possible that both kernel and drivers are native on ARM, I don't know, the emulated x86 apps however, run very slow. Here are some benchmarks from emulated and native apps on a snapdragon 835. https://www.techspot.com/review/1599-windows-on-arm-performance/page2.html Anyway, why would you wan...

Microsoft emulates x86 on ARM, there are already a few laptops with ARM architecture running this, the problem is that it runs so slow that it is not very usable in practice. Emulated x86 apps will be slow for sure (my guess about an order of magnitude even if JITted, just the cost of emulation its...

Eelco de Groot wrote: ↑

Thu Sep 20, 2018 8:47 am

For now, I don't think Windows 10 runs on ARM architecture.

I wouldn't be so sure https://docs.microsoft.com/en-us/windows/arm/

Does anybody know the exact difference between sched_yield() and usleep(0) or in windows Sleep(0) and SwitchToThread()? I don't know about Linux, but there's an attempt to recreate open source version of Windows (including kernel) called ReactOS. I'm not sure how much it resembles Windows kernel/sc...

Pawn cache helps, no doubt about that, I use it as well in my tuner. Your numbers indicate a speedup of 8% ((71.1-65.4)/71.1) for enabling eval cache. Ok, measurable at least but we can agree on the "not so stellar" :-) I think we can agree that the speedup would be 9% if you round properly :) Anyw...

But we came from the question whether eval cache may help for texel tuning, and here I still believe that it has no measurable influence if I assume that duplicate positions with different game results do occur as an exception only, and with mostly unique positions and cache clearing after each par...

I do not understand how an eval cache can help to speed up texel tuning. It depends on what positions you use, since I extracted the positions from actual self-play games, they weren't actually "random" positions but rather naturally sorted as the individual games progressed, that's why eval cache ...

I think using eval cache when tuning is an error, each time you modify a term and call the evaluator you will get the cached value instead of the new value. The same holds for quiescence, if you use TT pruning in quiescence you have to disable it. Not at all, you clear it before each iteration, so ...

I don't remember the times but IIRC eval cache helps a ton. Of course you want to parallelize as well.
Texel tuning is very fast because you don't have to play actual games.

Just wow. Congratulations!