Best Of

You don't need to explicitely create indexes as you would in traditional databases. Domo's automatically optimizes for performance. Slow performance may be due to complexity of the dashboard or an issue in how you have things structured.

One thing I always take into account when designing ETL Pipelines is to be a teapot - short and stout. What I mean is that you can filter the data as soon as you're able to and also selecting only the columns you need. This makes the data short and faster to process as there's less data. On the stout side of the coin, you'll want to make sure you do as many things in parallel when processing the data as possible. Instead of chaining joins together join other tables together as you can so multiple joins are happening at the same time. This will allow the parallelism to work efficiently and not have your pipeline waiting on steps slowing things down.

You would use the pivot/unpivot tile in Magic ETL: https://domo-support.domo.com/s/article/360044951294?language=en_US There are examples in the KB article that walk through exactly what you are trying to do. Let me know if you get stuck!