Timeline for How to be productive around constant 4-6 min interruptions while "slow" code runs?
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 4, 2023 at 21:54 | comment | added | Martin Maat | Yes. Did you ever try to run your jobs on less data and compare the results? If the difference in outcome is insignificant you might as well use the quick results. You may want to optimize in a different way: give it 30 seconds to produce results rather than use everything and make as quick as you can. Of course I don't know if that is even possible with the kind of jobs you are running. | |
| Dec 21, 2022 at 16:23 | comment | added | MYK | Preach. My working loop is usually "just get on with it" until I'm loosing ~1h a day to slow code. Then I spend a day making the code fast. Inevitably the code grows, so it get's slow again, etc... I've taken jobs from 7min to 12 seconds, but if you do 10 of those, etc... | |
| Dec 20, 2022 at 14:10 | history | answered | Doc Brown | CC BY-SA 4.0 |