# Analytical Workload
+ Performance tuning solutions are conflict with `OLTP` domain, e.g: indexing, blocksize, etc
+ E.g:
  + **`JOIN`**, **`GROUP BY`**, **`HAVING`**, **`AGGREGATION OPERATION`**, **`WINDOW OPERATION`**, **`ORDER BY`**, **`...`**
+ The de-facto solution: Columnar Storage

-----------------------------------------------------------
Data blocks accessing or scanning efficiency is not the only difference between the two workloads. It is not unusual when you try to trade off the performance for one side in order to improve the performance for the other. 

However, as long as two workloads exist in the same database on the same table, you cannot make both happy simultaneously.

For example, for block size OLAP prefers large blocks, while OLTP prefers relatively small block size.
