| 18:00 | awt | 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)? |
| 18:00 | asciilifeform | awt: there's no reason ever to 'check cpu usage' explicitly. what you want it a priority queue. |
| 18:01 | asciilifeform | i.e. all operations described in spec as 'if cpu cycles avail.' go to the bottom of said queue. |
| 18:01 | asciilifeform | (which is finite in size and items oughta be able to drop outta it undone after certain interval) |
| 18:01 | awt | asciilifeform: ah yes makes sense |
| 18:01 | asciilifeform | a++ |
| 18:02 | * | asciilifeform did not describe explicitly in spec how to do this, would make for even gnarlier and moar pedantic text than presently |
| 18:07 | awt | asciilifeform: was also considering wether to read all stored message hashes into memory on startup. |
| 18:07 | asciilifeform | awt: seems like 'premature optimization' imho |
| 18:09 | awt | 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. |
| 18:09 | asciilifeform | can e.g. read last hr on warmup. |
| 18:09 | awt | asciilifeform: indeed |