Greenplum database optimization - tips and tricks

There are couple of ways you can optimize the greenplum database. Bad performing queries may be the result of bad database design, improper distribution keys, badly written SQL and improper allocation of system resources. we will focus on
  1. Optimizing Data Distribution
  2. Optimizing Database Design
  3. Optimizing SQL Queries

Subscribe to posts

Optimizing Database Design

posted Oct 11, 2013, 8:21 AM by Sachchida Ojha   [ updated Oct 11, 2013, 8:28 AM ]

Many performance issues can be improved by database design. Review your database design and ask yourself the following: 
  1.  Does the schema reflect the way the data is accessed? 
  2.  Can larger tables be broken down into partitions? 
  3.  Are you using the smallest data type possible to store column values? 
  4.  Are columns used to join tables of the same data type? 
  5.  Are your indexes being used?

Optimizing Data Distribution

posted Oct 11, 2013, 8:19 AM by Sachchida Ojha

When you create a table in Greenplum Database, it is important to declare a distribution key that allows for even data distribution across all segments in the system. Because the segments work on a query in parallel, Greenplum Database will always be as fast as the slowest segment. If the data is unbalanced, the segments that have more data will return their results slower.

1-2 of 2