3 ms·

Really interesting article but I wish there was more data on the speed/performance of the Redshift queries. It seems to cover everything but the actual performa

• techprotocol 11y ago
  +1
  • zzleeper 11y ago
    Issues often accumulate content-less “+1” comments which serve only to spam the maintainers and any others subscribed to the issue. These +1s serve a valuable function in letting maintainers know how widespread an issue is, but their drawbacks are too great. We’d like issues to gain a first-class voting system, and for content-less comments like “+1” or “:+1:” or “me too” to trigger a warning and instructions on how to use the voting mechanism.
• JimmyAustin 11y ago
  From my experience analysing similar sized datasets, it really comes down to the structure of the query and dataset. If you nail your dist keys and your queries don't have many large joins, it's incredibly quick. If your dist keys aren't great and you have many joins, it will take a long long time.
  • stingraycharles 11y ago
    Exactly. You have to keep in mind that other than distkeys / sortkeys, there are no indexes. So all you can do to speed things up is organize your data better. For a ballpark figure, we work with a ~ 500million rows / 12 columns data set, and complex queries with a lot of joins typically take around 10 - 20 minutes to complete on Redshift's smallest cluster ($250/m).
• aerioux 11y ago
  Same^ This was great for "how to move postgres -> redshift" but i didnt learn anything about the title of the post ...