Analyse UI performance, fix low-hanging-fruit items #90
Labels
bug
Something isn't working
good first issue
Good for newcomers
help wanted
Extra attention is needed
Web
Web UI issues
I think some of the design choices in the UI implementation have bad performance characteristics. For example, we update the I/O and Alarm status panels after every instruction. This could be the reason why it takes the simulator several seconds to read the 360 lines of the "hello.tape" example program even though (1) the data is in memory, and (2) the simulated tape reader should be able to do this in under a second.
I'd like this code to be usable on portable devices (e.g. tablets) and it needs to not eat battery.
The text was updated successfully, but these errors were encountered: