Databases Reference
In-Depth Information
In the above example,
DLSINGLETHREADPERSTAGE
is set to
FALSE
, so this tells the
Essbase server not to use single threaded data loading on the Esscar application
and the
DLTHREADPREPARE
and
DLTHREADSWRITE
settings are used.
These settings will improve the performance of the Essbase data loads.
Well, there you have it. What was going to be a little bit about the
essbase.cfg
file has turned into quite a long-winded affair. That's okay, because there is a lot
to know, and a lot that can have a positive effect on your operations.
Memory management
Oh look, here is more information that could be in the
essbase.cfg
section. Yes,
that is true, but memory management is probably the most important task you can
perform to keep your Essbase system running smoothly and efficiently.
It's no secret that everything in life is a give and take. With Essbase, it gives you
unparalleled capacity for slicing and dicing large amounts of data, all the while
performing real time calculations on the fly. What Essbase takes for this is unbelievably
large amounts of memory to deliver this functionality with anywhere near acceptable
response times.
Before we talk about some of the
essbase.cfg
settings you can use to help control
your system's memory usage we want to discuss a few other things you can do:
1.
Make sure all of your applications and databases are set to only start when
there is a request for data and not when the analytic service starts. For every
started database, Essbase will reserve the memory necessary for that database
and there will be that much less memory available for the rest of the system.
2.
Create a small job that will run periodically and stop applications and
databases that are not actively in use, because in Essbase, once the
application or database is started, the only thing that stops it is a server
shutdown, the administrator, or by a command from a script or job.
3.
Monitor and adjust all caches and buffer settings, since they all use memory.
4.
Make judicious use of the
config.mem
file located in the
ArborPath\Bin
folder. This file allows you to set a maximum amount of memory to be used by
either specific applications or by all applications on the server. If an application
uses its maximum allotment of memory, it will either shutdown or slow way
down and attempt to process with what it has. This is a very important setting
because you do not want one application sucking all of the memory out of the
system and halting the other databases and their processes.
