Livienne spent about 2 hours (well, she said about more than 1 hr 45 mins but less than 2 hours, she likes being specific) on Tableau since we last spoke.
Here is a video of her work so far using cereal data
Livienne spent about 2 hours (well, she said about more than 1 hr 45 mins but less than 2 hours, she likes being specific) on Tableau since we last spoke.
Here is a video of her work so far using cereal data
Today we continued from where we left off yesterday and build some maps
Our first video where we picked data about volcanoes
So, if you have worked with Tableau, this is a question you have either asked or have been asked (or at least) wondered about?
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.
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
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?
Continue reading How do I conduct scalability testing with TabJolt