Timeline for When to really focus on performance?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 5, 2013 at 14:48 | vote | accept | Rayshawn | ||
| Jul 5, 2013 at 5:32 | comment | added | jwenting | Good example of Steven's answer: during my graduation work I was running experiments which took 12-48 hours to collect a single set of data for my thesis, I needed several dozen such sets. I couldn't care less if the software I was using took hours to process the results of each run, as long as it was done before the next run was complete. | |
| Jul 5, 2013 at 5:30 | comment | added | jwenting | @RayEatmon precompiling queries and preloading caches (which is what you're achieving by running that) is often a good way to flatten out performance spikes like that. | |
| Jul 5, 2013 at 4:15 | comment | added | Rayshawn | It's just one specific query that takes parameters. I did look a little into running the query immediately after deployment. That might be the best option for the moment. | |
| Jul 5, 2013 at 4:08 | history | answered | user53141 | CC BY-SA 3.0 |