Timeline for Relevance of optimization techniques
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 28, 2020 at 14:41 | comment | added | anatolyg | Sometimes, (or, where I work, always) "performance requirements" are vague - something like "it should be as slow as possible, but not so slow that your customer rejects your product". In absence of real requirements, step 5 in the answer above will be subjective. | |
| Jan 20, 2020 at 16:56 | vote | accept | JayZ | ||
| Jan 16, 2020 at 20:40 | history | edited | Robert Harvey | CC BY-SA 4.0 |
added 29 characters in body
|
| Jan 16, 2020 at 19:39 | history | edited | Robert Harvey | CC BY-SA 4.0 |
added 41 characters in body
|
| Jan 16, 2020 at 19:08 | comment | added | Berin Loritsch | I think step one is to "define good enough performance". Optimization problems can force you to do things in a less than clean way, so if you pretty much are already fast enough you don't have to keep squeezing blood from a stone. | |
| Jan 16, 2020 at 17:38 | history | edited | Robert Harvey | CC BY-SA 4.0 |
added 12 characters in body
|
| Jan 16, 2020 at 15:30 | history | edited | Robert Harvey | CC BY-SA 4.0 |
added 147 characters in body
|
| Jan 15, 2020 at 19:27 | history | edited | Robert Harvey | CC BY-SA 4.0 |
added 195 characters in body
|
| Jan 15, 2020 at 17:24 | history | edited | Robert Harvey | CC BY-SA 4.0 |
added 4 characters in body
|
| Jan 15, 2020 at 17:17 | history | answered | Robert Harvey | CC BY-SA 4.0 |