Recently I had an opportunity to work with a Product Data Distribution Optimizer (DDO) and I would like to share the experience with you all.
Before getting into the details of the product DDO, let’s try to understand the problem statement for why this product and when we need this product.
Let assume a use case:
We have one HANA box and we are running multiple applications on top of it. As show in picture below.
Each application will have their own schemas and tables. When we have multiple applications on Scaled out System (multi Node system), then it all depends upon how the user wanted to handle the system. Because when we have many applications on a bigger HANA box we face two problems from administration and performance point of view
Problem1: How to handle large number of tables:
1) First let’s assume that user is not handling anything, and each application has tables as shown below
And HANA takes a decision to distribute tables equally across nodes for evenly distributing the memory
So Now
Node1 has 3 Tables
Node2 has 3 Tables
Node3 has 3 Tables
Node4 has 3 Tables
Node5 has 3 Tables
Node6 has 2 Tables
How does this look? Tables are equally distributed across nodes thus even distribution of Load, that’s good. But what happens when I query on BW , almost all the nodes get accessed and this may bring your query performance down
2) When we have Bigger HANA box and running multiple application on top of it, then its better user controls the table location
What do I mean by that? Can user reserve nodes for their application? for an example
Node1 has 3 Tables
Node2 has 3 Tables
Node3 has 2 Tables
Node4 has 3 Tables
Node5 has 3 Tables
Node6 has 3 Tables
How does this look ? Tables are equally distributed across nodes thus even distribution of Load, that’s good. And Tables are also grouped and placed accordingly .This also ensures that when a query is fired from specific application then the number of Nodes accessed is less and which in turn yield you good performance.
Problem 2: How to Handle Large Tables
1) If user doesn’t handle anything, then we have two problems
2) User is handling the bigger table by smartly partitioning it
So now it’s clear that when we have multiple applications then it’s better to handle the
1) Table placement
2) Table partition
How to do that ? You can do it in HANA studio at
Now understanding the use case and existing solution, let’s get into our Tool “DDO”
The DDO tool is an XS based application developed to handle such administration kind of activities.
The DDO tool will help you to manage the tables and partitions at system level and with more control in a Scale out landscape.
Use Case of DDO
Functionalities
If you like to see how to use the tool and how the tool works you can watch the video
More links:
Hope this is helpful..
Thanks & Regards
A.Dinesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
38 | |
19 | |
13 | |
13 | |
11 | |
10 | |
10 | |
10 | |
8 | |
8 |