![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
We are having a problem with our OLAP server. It seems to sit at 25 to 35% processor busy even with no activity. Using performance monitor this appears to occur after partitions are processed in several cubes. Once the processing has completed it appears to continue to use 25% to 35% of the processor. 1. Processor Usages Sits at 25 to 35% busy 2. According to Performance Monitor "Analysis Server:Connection" there are zero "Current Connections" or "http Connections" 3. According to Performance Monitor "Analysis Server: Proc Aggs" 1 Partition is currently being processed even though no processing is occurring 4. According to Performance Monitor "Analysis Server: Proc Indexes" 1 Partition is currently being processed even though no processing is occurring 5. According to Performance Monitor "Analysis Server: Proc" 0 Partitions currently being processed 6. The Process text log shows no processing occurring 7. The server remains in this state for hours on end 8. Taskmgr shows msmdsrv.exe as the only task using the processor 9. When the processor finally returns to 0% busy several hours later the "Analysis Server: Proc Aggs" and "Analysis Server: Proc Indexes" both return to zero. Server Specs: Windows 2003 Service Pack 1 and all patches installed MSOLAP 2000 with Service Pack 4 4 Gigs of RAM with /3GB switch 2 Intel Xeon Processors 2.40 Ghz Maximum Number of threads: 8 Large level defined as: 1000 Minimum Allocated memory: 1024 Memory conservation threshold: 2048 Read ahead buffer: 40 Process buffer size: 2000 Write to log once per 50 queries |
#3
| |||
| |||
|
|
do you have lazy aggregation partitions? a lazy aggregation option will evaluate the aggregations of a partition when the server is IDLE instead of evaluate the aggregation during the processing time. this can cause a long and slower processing time, but the cube become available more quickly to the end user. but during this background aggregation the server is slower. regarding the information in the performance counters, this indicates that you have a lazy aggregation process running. "davids (AT) thorntonsinc (DOT) com" <davidsthorntonsinccom (AT) discussions (DOT) microsoft.com wrote We are having a problem with our OLAP server. It seems to sit at 25 to 35% processor busy even with no activity. Using performance monitor this appears to occur after partitions are processed in several cubes. Once the processing has completed it appears to continue to use 25% to 35% of the processor. 1. Processor Usages Sits at 25 to 35% busy 2. According to Performance Monitor "Analysis Server:Connection" there are zero "Current Connections" or "http Connections" 3. According to Performance Monitor "Analysis Server: Proc Aggs" 1 Partition is currently being processed even though no processing is occurring 4. According to Performance Monitor "Analysis Server: Proc Indexes" 1 Partition is currently being processed even though no processing is occurring 5. According to Performance Monitor "Analysis Server: Proc" 0 Partitions currently being processed 6. The Process text log shows no processing occurring 7. The server remains in this state for hours on end 8. Taskmgr shows msmdsrv.exe as the only task using the processor 9. When the processor finally returns to 0% busy several hours later the "Analysis Server: Proc Aggs" and "Analysis Server: Proc Indexes" both return to zero. Server Specs: Windows 2003 Service Pack 1 and all patches installed MSOLAP 2000 with Service Pack 4 4 Gigs of RAM with /3GB switch 2 Intel Xeon Processors 2.40 Ghz Maximum Number of threads: 8 Large level defined as: 1000 Minimum Allocated memory: 1024 Memory conservation threshold: 2048 Read ahead buffer: 40 Process buffer size: 2000 Write to log once per 50 queries |
#4
| |||
| |||
|
|
From some other things I have read I figured that was go I also found files in the AS folder called: Partition2006200603200609.18.agg.flex.map which seems to indicate that this is going on. How do you turn it off? "Jeje" wrote: do you have lazy aggregation partitions? a lazy aggregation option will evaluate the aggregations of a partition when the server is IDLE instead of evaluate the aggregation during the processing time. this can cause a long and slower processing time, but the cube become available more quickly to the end user. but during this background aggregation the server is slower. regarding the information in the performance counters, this indicates that you have a lazy aggregation process running. "davids (AT) thorntonsinc (DOT) com" davidsthorntonsinccom (AT) discussio... microsoft.com wrote in message news:E06C6E0E-1A66-426E-A483-B040CEFAD36E (AT) microsoft (DOT) com... We are having a problem with our OLAP server. It seems to sit at 25 to 35% processor busy even with no activity. Using performance monitor this appears to occur after partitions are processed in several cubes. Once the processing has completed it appears to continue to use 25% to 35% of the processor. 1. Processor Usages Sits at 25 to 35% busy 2. According to Performance Monitor "Analysis Server:Connection" there are zero "Current Connections" or "http Connections" 3. According to Performance Monitor "Analysis Server: Proc Aggs" 1 Partition is currently being processed even though no processing is occurring 4. According to Performance Monitor "Analysis Server: Proc Indexes" 1 Partition is currently being processed even though no processing is occurring 5. According to Performance Monitor "Analysis Server: Proc" 0 Partitions currently being processed 6. The Process text log shows no processing occurring 7. The server remains in this state for hours on end 8. Taskmgr shows msmdsrv.exe as the only task using the processor 9. When the processor finally returns to 0% busy several hours later the "Analysis Server: Proc Aggs" and "Analysis Server: Proc Indexes" both return to zero. Server Specs: Windows 2003 Service Pack 1 and all patches installed MSOLAP 2000 with Service Pack 4 4 Gigs of RAM with /3GB switch 2 Intel Xeon Processors 2.40 Ghz Maximum Number of threads: 8 Large level defined as: 1000 Minimum Allocated memory: 1024 Memory conservation threshold: 2048 Read ahead buffer: 40 Process buffer size: 2000 Write to log once per 50 queries |
#5
| |||
| |||
|
|
Right click on the cube, select process, then go in the settings page and you have 2 choices in the processing optimization mode. if you have selected the second option, then your aggregations are calculated in background. the other place to find this option is to edit the cube himself. then open the advanced tab in the properties pane and you have the "processing optimization mode" option. "davids (AT) thorntonsinc (DOT) com" <davidsthorntonsinccom (AT) discussions (DOT) microsoft.com wrote From some other things I have read I figured that was go I also found files in the AS folder called: Partition2006200603200609.18.agg.flex.map which seems to indicate that this is going on. How do you turn it off? "Jeje" wrote: do you have lazy aggregation partitions? a lazy aggregation option will evaluate the aggregations of a partition when the server is IDLE instead of evaluate the aggregation during the processing time. this can cause a long and slower processing time, but the cube become available more quickly to the end user. but during this background aggregation the server is slower. regarding the information in the performance counters, this indicates that you have a lazy aggregation process running. "davids (AT) thorntonsinc (DOT) com" davidsthorntonsinccom (AT) discussio... microsoft.com wrote in message news:E06C6E0E-1A66-426E-A483-B040CEFAD36E (AT) microsoft (DOT) com... We are having a problem with our OLAP server. It seems to sit at 25 to 35% processor busy even with no activity. Using performance monitor this appears to occur after partitions are processed in several cubes. Once the processing has completed it appears to continue to use 25% to 35% of the processor. 1. Processor Usages Sits at 25 to 35% busy 2. According to Performance Monitor "Analysis Server:Connection" there are zero "Current Connections" or "http Connections" 3. According to Performance Monitor "Analysis Server: Proc Aggs" 1 Partition is currently being processed even though no processing is occurring 4. According to Performance Monitor "Analysis Server: Proc Indexes" 1 Partition is currently being processed even though no processing is occurring 5. According to Performance Monitor "Analysis Server: Proc" 0 Partitions currently being processed 6. The Process text log shows no processing occurring 7. The server remains in this state for hours on end 8. Taskmgr shows msmdsrv.exe as the only task using the processor 9. When the processor finally returns to 0% busy several hours later the "Analysis Server: Proc Aggs" and "Analysis Server: Proc Indexes" both return to zero. Server Specs: Windows 2003 Service Pack 1 and all patches installed MSOLAP 2000 with Service Pack 4 4 Gigs of RAM with /3GB switch 2 Intel Xeon Processors 2.40 Ghz Maximum Number of threads: 8 Large level defined as: 1000 Minimum Allocated memory: 1024 Memory conservation threshold: 2048 Read ahead buffer: 40 Process buffer size: 2000 Write to log once per 50 queries |
#6
| |||
| |||
|
|
I checked the cube and on the advanced tab it is set to regular NOT to "lazy aggregation" is there anything else that could be causing it to do "lazy aggregation"? "Jeje" wrote: Right click on the cube, select process, then go in the settings page and you have 2 choices in the processing optimization mode. if you have selected the second option, then your aggregations are calculated in background. the other place to find this option is to edit the cube himself. then open the advanced tab in the properties pane and you have the "processing optimization mode" option. "davids (AT) thorntonsinc (DOT) com" davidsthorntonsinccom (AT) discussio... microsoft.com wrote in message news:BDF41E4B-7A0F-4B10-8D9D-DD18594AD4D4 (AT) microsoft (DOT) com... From some other things I have read I figured that was go I also found files in the AS folder called: Partition2006200603200609.18.agg.flex.map which seems to indicate that this is going on. How do you turn it off? "Jeje" wrote: do you have lazy aggregation partitions? a lazy aggregation option will evaluate the aggregations of a partition when the server is IDLE instead of evaluate the aggregation during the processing time. this can cause a long and slower processing time, but the cube become available more quickly to the end user. but during this background aggregation the server is slower. regarding the information in the performance counters, this indicates that you have a lazy aggregation process running. "davids (AT) thorntonsinc (DOT) com" davidsthorntonsinccom (AT) discussio... microsoft.com wrote in message news:E06C6E0E-1A66-426E-A483-B040CEFAD36E (AT) microsoft (DOT) com... We are having a problem with our OLAP server. It seems to sit at 25 to 35% processor busy even with no activity. Using performance monitor this appears to occur after partitions are processed in several cubes. Once the processing has completed it appears to continue to use 25% to 35% of the processor. 1. Processor Usages Sits at 25 to 35% busy 2. According to Performance Monitor "Analysis Server:Connection" there are zero "Current Connections" or "http Connections" 3. According to Performance Monitor "Analysis Server: Proc Aggs" 1 Partition is currently being processed even though no processing is occurring 4. According to Performance Monitor "Analysis Server: Proc Indexes" 1 Partition is currently being processed even though no processing is occurring 5. According to Performance Monitor "Analysis Server: Proc" 0 Partitions currently being processed 6. The Process text log shows no processing occurring 7. The server remains in this state for hours on end 8. Taskmgr shows msmdsrv.exe as the only task using the processor 9. When the processor finally returns to 0% busy several hours later the "Analysis Server: Proc Aggs" and "Analysis Server: Proc Indexes" both return to zero. Server Specs: Windows 2003 Service Pack 1 and all patches installed MSOLAP 2000 with Service Pack 4 4 Gigs of RAM with /3GB switch 2 Intel Xeon Processors 2.40 Ghz Maximum Number of threads: 8 Large level defined as: 1000 Minimum Allocated memory: 1024 Memory conservation threshold: 2048 Read ahead buffer: 40 Process buffer size: 2000 Write to log once per 50 queries |
#7
| |||
| |||
|
|
how do you process your cubes? do you do it manually? or through a tool or batch file? because this option can be setup when you ask for a process, if you use a tool, then verify these options. if you really not have this option enable anywhere, then I don't know what's appends and maybe somebody else can help you. "davids (AT) thorntonsinc (DOT) com" <davidsthorntonsinccom (AT) discussions (DOT) microsoft.com wrote I checked the cube and on the advanced tab it is set to regular NOT to "lazy aggregation" is there anything else that could be causing it to do "lazy aggregation"? "Jeje" wrote: Right click on the cube, select process, then go in the settings page and you have 2 choices in the processing optimization mode. if you have selected the second option, then your aggregations are calculated in background. the other place to find this option is to edit the cube himself. then open the advanced tab in the properties pane and you have the "processing optimization mode" option. "davids (AT) thorntonsinc (DOT) com" davidsthorntonsinccom (AT) discussio... microsoft.com wrote in message news:BDF41E4B-7A0F-4B10-8D9D-DD18594AD4D4 (AT) microsoft (DOT) com... From some other things I have read I figured that was go I also found files in the AS folder called: Partition2006200603200609.18.agg.flex.map which seems to indicate that this is going on. How do you turn it off? "Jeje" wrote: do you have lazy aggregation partitions? a lazy aggregation option will evaluate the aggregations of a partition when the server is IDLE instead of evaluate the aggregation during the processing time. this can cause a long and slower processing time, but the cube become available more quickly to the end user. but during this background aggregation the server is slower. regarding the information in the performance counters, this indicates that you have a lazy aggregation process running. "davids (AT) thorntonsinc (DOT) com" davidsthorntonsinccom (AT) discussio... microsoft.com wrote in message news:E06C6E0E-1A66-426E-A483-B040CEFAD36E (AT) microsoft (DOT) com... We are having a problem with our OLAP server. It seems to sit at 25 to 35% processor busy even with no activity. Using performance monitor this appears to occur after partitions are processed in several cubes. Once the processing has completed it appears to continue to use 25% to 35% of the processor. 1. Processor Usages Sits at 25 to 35% busy 2. According to Performance Monitor "Analysis Server:Connection" there are zero "Current Connections" or "http Connections" 3. According to Performance Monitor "Analysis Server: Proc Aggs" 1 Partition is currently being processed even though no processing is occurring 4. According to Performance Monitor "Analysis Server: Proc Indexes" 1 Partition is currently being processed even though no processing is occurring 5. According to Performance Monitor "Analysis Server: Proc" 0 Partitions currently being processed 6. The Process text log shows no processing occurring 7. The server remains in this state for hours on end 8. Taskmgr shows msmdsrv.exe as the only task using the processor 9. When the processor finally returns to 0% busy several hours later the "Analysis Server: Proc Aggs" and "Analysis Server: Proc Indexes" both return to zero. Server Specs: Windows 2003 Service Pack 1 and all patches installed MSOLAP 2000 with Service Pack 4 4 Gigs of RAM with /3GB switch 2 Intel Xeon Processors 2.40 Ghz Maximum Number of threads: 8 Large level defined as: 1000 Minimum Allocated memory: 1024 Memory conservation threshold: 2048 Read ahead buffer: 40 Process buffer size: 2000 Write to log once per 50 queries |
![]() |
| Thread Tools | |
| Display Modes | |
| |