Featured Post

SQL Interview Success: Unlocking the Top 5 Frequently Asked Queries

Image
 Here are the five top commonly asked SQL queries in the interviews. These you can expect in Data Analyst, or, Data Engineer interviews. Top SQL Queries for Interviews 01. Joins The commonly asked question pertains to providing two tables, determining the number of rows that will return on various join types, and the resultant. Table1 -------- id ---- 1 1 2 3 Table2 -------- id ---- 1 3 1 NULL Output ------- Inner join --------------- 5 rows will return The result will be: =============== 1  1 1   1 1   1 1    1 3    3 02. Substring and Concat Here, we need to write an SQL query to make the upper case of the first letter and the small case of the remaining letter. Table1 ------ ename ===== raJu venKat kRIshna Solution: ========== SELECT CONCAT(UPPER(SUBSTRING(name, 1, 1)), LOWER(SUBSTRING(name, 2))) AS capitalized_name FROM Table1; 03. Case statement SQL Query ========= SELECT Code1, Code2,      CASE         WHEN Code1 = 'A' AND Code2 = 'AA' THEN "A" | "A

2 Scaling-Up And Scaling-out QlikView's Ideas! That You Can Never Miss

In scale-up architecture

A single server is used to serve the QlikView applications. In this case, as more throughput is required, bigger and/or faster hardware (e.g. with more RAM and/or CPU capacity) are added to the same server.

Scale-up
The Scale-up architecture


In scale-out architecture

More servers are added when more throughput is needed to achieve the performance necessary. It is common to see the use of commodity servers in these types of architectures. 

As more throughput is required new servers are added, creating a clustered QlikView environment. In these environments, QlikView Server supports load sharing of QlikView applications across multiple physical or logical computers. 

QlikView load balancing refers to the ability to distribute the load (i.e. end-user sessions) across the cluster in accordance with a predefined algorithm for selecting which node should take care of a certain session. QlikView Server version 11 supports three different load balancing algorithms.

Below is a brief definition of each scheme. Please refer to the QlikView Scalability Overview Technology white paper for further details. 

Scale-out
The scale-out Architecture
 
Random: The default load-balancing scheme. The user is sent to a random server, no matter if the QlikView application the user is looking for is loaded or not on a QlikView Server. 
 
Loaded Document: If only one QlikView Server has the particular QlikView application loaded, the user is sent to that QlikView Server. If more than one QlikView Server or none of the QlikView Servers have the application loaded, the user is sent to the QlikView Server with the largest amount of free RAM. 

CPU with RAM Overload: The user is sent to the least busy QlikView Server. Please note that this report does not go into detail on when to use and how to tune different load balancing algorithms for best performance. 

Cluster test executions presented in this report has been run in an environment configured with a better performing scheme for certain conditions of a particular test.

Comments

Popular posts from this blog

How to Fix datetime Import Error in Python Quickly

Explained Ideal Structure of Python Class

How to Check Kafka Available Brokers