![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi: I read from an article "OLAP Services: Performance Implications of the Architecture" from link below. http://msdn.microsoft.com/library/de...l/olapperf.asp Here is part of the article that talking about using DSO to implement parallel processing of the two threads: Reader and the Processing/Aggregation thread. I have never noticed DSO ability for utilizing parallel processing of those two threads. I'm not sure if the utility you have mentioned is for such purpose? Thanks. Internal Implementation Processing members and facts is a double-buffered scheme and is implemented using the following threads: 1.. The Reader thread populates the Read Ahead buffer with records read from the data source. 2.. The Processing/Aggregation thread processes this data, saves the data in a segment, and optionally creates any requested aggregations. 3.. These two threads work in parallel and therefore a maximum of two processors can be utilized while processing a partition. The server's ability to process multiple cubes in parallel provides a big boost to processing performance. Currently, the OLAP Manager does not offer this implementation through the user interface. However, DSO does provide a means of implementation. 4.. To reduce the working set needed during processing, the fact table is divided into a group of 64K (or multiples of 64K) records. These groups are called segments and one segment at a time is processed. "Sean Boon [MS]" <seanboon (AT) online (DOT) microsoft.com> wrote in message news:uIlvsWPbDHA.2580 (AT) TK2MSFTNGP09 (DOT) phx.gbl... Polaris, I'm not sure I understand your question, however the parallel process utility in the SQL 2k resource kit comes with the source code. Sean -- Sean Boon SQL Server BI Product Unit -- This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm. "Polaris" <etpolaris (AT) hotmail (DOT) com> wrote in message news:OIdcr7ObDHA.384 (AT) TK2MSFTNGP12 (DOT) phx.gbl... Hi : Any one knows DSO functions used to implement parallel processing of the two threads: "Reader" thread and "Processing/Aggregation" thread ? THanks |
#3
| |||
| |||
|
|
The information below is correct. What is it that you are not seeing? If you issue a full process against a paritition using the processfull method on the partition object in DSO, this will happen on it's own. You don't need to write custom code to take advantage of this behavior within the process funcion itself. Sean -- Sean Boon SQL Server BI Product Unit -- This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm. "Polaris" <etpolaris (AT) hotmail (DOT) com> wrote in message news:eY4$VoPbDHA.2580 (AT) TK2MSFTNGP12 (DOT) phx.gbl... Hi: I read from an article "OLAP Services: Performance Implications of the Architecture" from link below. http://msdn.microsoft.com/library/de...l/olapperf.asp Here is part of the article that talking about using DSO to implement parallel processing of the two threads: Reader and the Processing/Aggregation thread. I have never noticed DSO ability for utilizing parallel processing of those two threads. I'm not sure if the utility you have mentioned is for such purpose? Thanks. Internal Implementation Processing members and facts is a double-buffered scheme and is implemented using the following threads: 1.. The Reader thread populates the Read Ahead buffer with records read from the data source. 2.. The Processing/Aggregation thread processes this data, saves the data in a segment, and optionally creates any requested aggregations. 3.. These two threads work in parallel and therefore a maximum of two processors can be utilized while processing a partition. The server's ability to process multiple cubes in parallel provides a big boost to processing performance. Currently, the OLAP Manager does not offer this implementation through the user interface. However, DSO does provide a means of implementation. 4.. To reduce the working set needed during processing, the fact table is divided into a group of 64K (or multiples of 64K) records. These groups are called segments and one segment at a time is processed. "Sean Boon [MS]" <seanboon (AT) online (DOT) microsoft.com> wrote in message news:uIlvsWPbDHA.2580 (AT) TK2MSFTNGP09 (DOT) phx.gbl... Polaris, I'm not sure I understand your question, however the parallel process utility in the SQL 2k resource kit comes with the source code. Sean -- Sean Boon SQL Server BI Product Unit -- This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm. "Polaris" <etpolaris (AT) hotmail (DOT) com> wrote in message news:OIdcr7ObDHA.384 (AT) TK2MSFTNGP12 (DOT) phx.gbl... Hi : Any one knows DSO functions used to implement parallel processing of the two threads: "Reader" thread and "Processing/Aggregation" thread ? THanks |
![]() |
| Thread Tools | |
| Display Modes | |
| |