Enjoy a Tableau visual showing results of all US elections till 2012
So, you have worked on creating a wonderful dashboard for your executives but you want to provide the graphs with some titles so your team can quickly see the numbers too.
Here’s how you might have been doing that for now
But, what about the total numbers?
Yup, you are creating new sheets to do just the metrics. Well, no need, anymore
Here are the tips to add the total of a metric (or metrics for that matter) within the sheet so you can create more insightful dashboards.
So, I have been in consulting for a very long time and I have been capturing a lot of detail over the last decade over or so in a database.
Finally, decided to open that database in Tableau and spend a few hours creating a dashboard…
Now, I can see how many projects have I worked on, which project required least amount of travel, what sort of activity have been I been working on mostly, etc. etc.
One of the customers recently asked me “what happens when I click performance recording” in Tableau?
Now, what was surprising was, that this person, who is proficient in Tableau Desktop was asking me the question. Which made me wonder, why?
Why, did he just not click it himself and see what happens?
I think there is a mix of reasons behind why a lot of people haven’t clicked this option. Continue reading “What happens when I click the Performance Recording in Tableau?”
So, if you have worked with Tableau, this is a question you have either asked or have been asked (or at least) wondered about?
Why would you want to use a TDE (aka DATA Extracts)?
If you are in business side of things you will probably be wondering why you even need to make this decision. This is an IT decision, typically. isn’t it?
If you are on the IT end of the business (pun intended), you might say, what the heck?
I have to maintain another source of data?
so, let’s get some things straight today.
This article will help you understand the what, the why and the how if the TDEs.
well, at least my perspective on it, anyway.
Ok, so you ran a bunch of tests using TabJolt. What next?
You are probably here because you read the article on how to conduct scalability testing
The first thing that you should do is extract the data out of postgres rather than making live connections.
Then, you get confused with all the results that you see in the workbook. What are you supposed to make out of all those numbers?
If you have never done any test of this kind before, you are in for a surprise.
At Tableau, we like to keep things simple. But, unfortunately, a lot of you see those test results seem anything but simple.
Here’s my take on it.
Before you setup a Tableau Server, you have a lot of questions
- Do I have enough servers for my users?
- How will my user mix (viewer/interactor) impact my server capacity planning?
- How many VizQLs do I need for my user community?
- Can I configure 8 VizQL instances on a single server?
- …… to name a few.
The idea behind this post is to guide you on how to do some of your own tests to get some of the answers
So, lets get started and understand a few things about scalability tests
The idea is to understand how many users of a particular type of load can a server support
Now, since I currently work for Tableau and have had exposure to some of their tools, I used one of their tools (TabJolt) to conduct some of the tests
The rest of the article follows an approach. You can most certainly follow the same approach and use a completely different tool
Getting Started with TabJolt
I don’t plan to re-invent the wheel so if you haven’t even started with TabJolt, please refer to this great blog on TabJolt
How do I start?