Confirmed users
513
edits
Klahnakoski (talk | contribs) m (fix link) |
Klahnakoski (talk | contribs) (wording, and split sections) |
||
| Line 124: | Line 124: | ||
==Philosophical Lesson== | ==Philosophical Lesson== | ||
It is apparent to me now that a performance comparison cannot be thorough without a product specialist to guide the optimization process. Absent of a specialist how can one decide if a new product is better? We run the risk of over analysis, driven by fear of missing a shallow optimization. Clearly, if the product performs better out-of-the-box than your existing, (assumed optimized) solution, then the answer is easy. But, even “out-of-the-box” can take a significant amount of time, like this case of Redshift. | |||
== More References === | |||
These links were a help, and are more relevant to scaling Redshift in general. | These links were a help, and are more relevant to scaling Redshift in general. | ||
* http://dailytechnology.net/2013/08/03/redshift-what-you-need-to-know/ | * http://dailytechnology.net/2013/08/03/redshift-what-you-need-to-know/ | ||
* http://blog.blazeclan.com/what-is-amazon-redshift-11-key-points-remember/ | * http://blog.blazeclan.com/what-is-amazon-redshift-11-key-points-remember/ | ||