Hi,
I am facing issue with our client related to Analysis Services 2005 using only 13% of CPU.
Our client is running on server with 8 CPUs, 15GB of RAM. When request being made to execute MDX, only 13% of CPU is utilized. It is like using only one CPU. When additional concurrent user is added, then CPU usage increases.
The Analaysis Services being used is Evaluation Copy at this point.
I checked all possible settings in Analysis Services, like to increase concurrent threads, and other settings, but it brings no result. CPU is stuck at 13% for single user.
So, is it like limitation of SQL Server Evaluation copy that it does not utilize full CPU, or Analysis Services is not meant to use more that 1 CPU (which is unlikely)?
Can you help me to troubleshoot this issue.
Thank you
Analysis Services OLAP engine is roughly divided into two major components: 1) query processor and calculation engine 2) storage engine. Storage engine is multithreaded to support parallel access to multiple partitions. The calculation engine is mainly singlethreaded. If your query is calculation intensive instead of data intensive, you would only see a single CPU maxed out.|||thanks for clarifying the internals of Analysis Services.
At the moment i have only one partition in the OLAP Database. The performance drop when several crossjoin statements used in the MDX. I will try to optimize my mdx statements, but is there anyway to optimize calculation engine?
Will it help calculation engine if i divide my cube into several partitions? Our client data is pretty big, 1GB for 8 days data. Eventually, our client wants to keep 60 days data in the cube, and historical data being purged or archived. My intention was also eventually create partitions either monthly, or weekly as it is implemented in Project REAL.
So, what are the way you can suggest to optimize calculating engine?
Thank you.
No comments:
Post a Comment