awt[asciilifeform]: asciilifeform: For deciding when to retrieve a message from storage, would maybe checking cpu usage maybe be a good measure as to when to allow it (iirc this check also can be expensive)?
asciilifeform: awt: there's no reason ever to 'check cpu usage' explicitly. what you want it a priority queue.
asciilifeform: i.e. all operations described in spec as 'if cpu cycles avail.' go to the bottom of said queue.
asciilifeform: (which is finite in size and items oughta be able to drop outta it undone after certain interval)
awt[asciilifeform|billymg]: asciilifeform: ah yes makes sense
asciilifeform: a++
asciilifeform did not describe explicitly in spec how to do this, would make for even gnarlier and moar pedantic text than presently
awt[asciilifeform|billymg]: asciilifeform: was also considering wether to read all stored message hashes into memory on startup.
asciilifeform: awt: seems like 'premature optimization' imho
awt[asciilifeform|billymg]: Feels that way yes, although if they're not loaded, will have to check storage for hashes for the first hour after restart for each incoming message.
asciilifeform: can e.g. read last hr on warmup.
awt[asciilifeform]: asciilifeform: indeed