When you clicked on this blog, you might’ve thought, “…another tutorial about performance tuning.” Well, if you’re looking for an OBIEE tuning guide, this isn’t it.
The word “tuning” gets thrown around as a catchall phrase to describe correcting a tool’s performance. We use that same approach when we talk about tuning a car — an action that can refer to a simple oil change or a complete engine overhaul. But, as you can see by that example, tuning doesn’t account for the scope of the task.
In our world, it’s important to differentiate tuning from redesigning. Tuning refers to fixing performance issues while the overall design of your tool remains the same. If you must redevelop something in your system that’s going to take a lot of time, you’re definitely not tuning.
Why should you make this distinction? It ensures that your team or project manager understands the scope of the project you’re working on. If you make something sound less significant than it is, you’re doing a disservice to yourself and your team.
Now that we have the semantics out of the way, we can move on to the meatier stuff — showing you how to optimize (not tune) the design of OBIEE for the best performance.