S_P_A_R_T wrote:
After some review, it looks like I found the root issue of poor S3 performance! You see, after every move, WD updates the progress bar, on TW, this doesn't affect performance much but on S3, it's the difference between 18 NPS, and 136 NPS! (136 / 18 = 7.5x faster!)

Now the only problem is that the progress bar doesn't load along with the engine as it's in search.

Good news! If you want to trigger a screen update from a run-without-refresh custom block, the only way is to broadcast a message and repaint in message receiver. That is by using broadcast, not broadcast-and-wait (the latter will kill performance completely).