- Keep it simple.
- Use only the data you need.
- Use filters efficiently (use context filter if possible).
- Not all mark types are equals.
- Use Fixed dashboard size for the fastest loading. Automatic size is not recommended because Tableau will generate every time it is turned on.
- Data physics -> type data: number/bool > date >> string; CNTD most expensive.
- Use right calculation -> LOD paling pelan; R/phyton can be slow because must wait data serialized from/to R.
- Having your data all in one place is faster than pulling it from multiple sources.
- the less you have to manipulate your data, the faster it will be -> union, pivot, calculation, etc.
- Trust Tableau to do its job -> avoid customSQL and stores procedures.
- Tableau does lots of stuff to make your workbooks fast -> parallel execute.
Fix my data source design
- Extract are an easy way to make things go fast -> hide unused fields.
- Tune your database for optimal performance.
- Use data server for governance -> have data expert/stewards optimize the connections and share it with business users; use extracts across multiple workbooks/share extracts as possible.
- Use native drivers where available -> better than ODBC/JDBC
- Test query performance on the server.
- Use cold (raw) / warm (prepared) / hot (aggregated) strategies.
- Upgrade -> physical server faster; Tableau need RAM than CPU.
- Be prepared to test on the server.
- Keep interactive users and extract refreshes separated.
- Monitor and tune.
- Virtual vs physical -> Tableau need dedicated resources for the best performance, physical better than VM.
No comments:
Post a Comment