Message from JavaScript discussions

December 2018

— ^^^ determin1st


I could target "hot" functions and make an operand cache paired with an output cache, and the dependency analysis could inform it of whether or not it is appropriate to re-use old outputs rather than re-running a function

— Yeee

— Right now I haven't gotten to the multithreading stage yet, which is required to do the multiprocessing stage

Message permanent page

— Not using labels? :(

— Maybe only target functions that run for > n chunks

— Still considering it, just focused on other things atm

— To avoid creating caches at all for tiny ones

— I want to try the label idea

— Been working on CLI tools though

— Consume X ratio of the total available amount of CPU time

— Cool