Re: SSAS 2005 perform worse performance that 2000
- From: "Vimas" <Vimas@xxxxxxxxxxxxx>
- Date: Mon, 13 Nov 2006 08:56:05 -0500
When you say "migrate", do you mean you used Migration wizard, or you
actually re-designed system? There are so many changes in SSAS 2005 and in
my opinion you do need to adjust your design to take advatage of them.
Have you went through each dimension and adjusted attribute relationship?
How many dimensions and how big are some of them?
"Ramunas Balukonis" <ramblk2@xxxxxxxxxxx> wrote in message
news:1163056194.603024@xxxxxxxxxxxxxxxxxxxxx
Hi,
we have migrate our cubes from our 32 bit olap 2000 machine to x64 bit
2005.
But after migrating seems 2005 perform worse performance in many cases
that
2000. On our new server we have 8CPU and 64 GB of memory, i gave 20 GB to
sql server and leave all SSAS memory options default because MS does not
recomend change memory settings.
Our cube files takes about 35 GB, but database Estimated Size from cube
properties shows only 206 MB. Cube is partitioned.
Looking at perfom, I see that Total queries from file is about 2000, Total
queries from cache filtered 500000, Total queries from cache direct 30000.
So, only few percent of queries answered from files, all others - from
cache. In task manager msmdsrv takes 2 GB of memory. But in perfom MSAS
2005: Cache shows only 700 MB of memory and is the same as Memory
AggcacheKB. Is it OK?
Also, in the same MSAS 2005: Misses/sec is about 50 percent of
Lookups/sec.
Is it normal? So, every second query pass cache? Why?
Also, interesting case with counter MSAS 2005: Proc aggregations memory
size
bytes. I used this perfom in SQL 2000 to see is there any job creating
aggregates, especially it was usefull when I did incremental dimensions
update. In SQL 2005 this counter shows nonzero only when partitions
process
are in "aggregate" state. But when I do incremental update for dimensions
this counter always shows 0. Is it normal behaviour?
One more thing - do I need to specify "slice" property for the partition?
I
read abouty this option I need to set only for ROLAP partitions. I tried
to
set slice property, but the same result. I missed way to known how many
partitions is partcipating into olap query.
Please, is there any suggestions how to optimize SSAS 2005 cubes.
Ramunas Balukonis
.
- References:
- SSAS 2005 perform worse performance that 2000
- From: Ramunas Balukonis
- SSAS 2005 perform worse performance that 2000
- Prev by Date: Re: Rollup in one dimension of calculated members in another...
- Next by Date: Accessing lower level members
- Previous by thread: Re: SSAS 2005 perform worse performance that 2000
- Next by thread: ADOMD & COM Interop
- Index(es):
Relevant Pages
|
