COGNOS Business Intelligence Series 7
pes.pdf pes.pdf
Chapter 3: Control Processes 2. From the Edit menu, click Properties, and then click the Settings tab. 3. In the Maximum Processes box (Process Control), type the number of processes. 4. If you have defined mirror references and want to give processing preferences to the local source in order to queue requests rather than forward them to the mirror reference, type the number of requests to queue (beyond the maximum) in the Local Process Threshold box. 5. Click OK. Tips • If, after adjusting the number of processes, you determine that more processing power is required, you can use mirror references to process remotely, or you may need to upgrade your computing resources. Limit the Processing Time You can set an absolute time limit that the query or report processor spends on any request. Adjusting this timeout may be useful for cases of "runaway" queries that would otherwise consume up to 15 minutes (the default) of processor time. Steps 1. In PowerPlay Enterprise - Server Administration, select a cube or report. 2. From the Edit menu, click Properties, and then click the Settings tab. 3. In the Request Timeout box (Process Control), type the number of seconds. 4. Click OK. Tips • This setting applies to all requests submitted by all users. Setting it too low may result in a high number of query or report failures. Configure How Windows Processes are Scheduled As a new request is received from a PowerPlay Windows application, there may be a delay before that request gets processed by a query processor (if it is busy). For any cube, you can choose how to distribute requests based on how busy each processor is, by setting a threshold to control the load balancing for these requests. The setting represents a ratio of delay time to active processing time. • A value of 0 means no delay, so each request is submitted to the first available processor, similar to the way Web requests are handled. • A value from 1 to 9 means each request is submitted to the next processor whose ratio of delay time to processing time is lower than the number specified. For example, a value of 5 means each request is submitted to the first processor that has less than a 50% ratio of delay time to processing time. • A value of 10 means each request is submitted to the next processor in sequence, regardless of the load on that processor. Steps 1. In PowerPlay Enterprise - Server Administration, select a cube. 2. From the Edit menu, click Properties, and then click the Settings tab. 3. In the Scheduling Threshold(s) box (Process Control), type a number from 0 to 10. 4. Click OK. Stop Processing Requests You can disable a PowerPlay server, folder, or individual cubes or reports to temporarily prevent the processor from accepting requests. This is useful, for example, when you have to replace a cube or report, or perform maintenance on several items at once. You can also use this feature to stop any runaway processes. 34 Cognos PowerPlay (R)
Chapter 3: Control Processes When you stop the processing, the following dialog box appears. If you select Stop After all Requests Are Complete, the server stops accepting new requests, including any in the queue, but requests that are being processed continue until they are finished. You can monitor the processes in the Monitor tab of PowerPlay Enterprise - Server Administration. If you select Stop Immediately, the server stops processing requests. Steps 1. In PowerPlay Enterprise - Server Administration, select an item. 2. From the Actions menu, click Stop. 3. Select one of the stop options. 4. Click OK. Notes • Selecting a server and stopping it is not the same as shutting it down (p. 15), but rather like stopping the processes of an implied folder at the root level. • If you are using the ppadmtool in Windows or on UNIX, you can stop processes by typing KILL and then the object name; for example, you can stop processes against the Great Outdoors cube by typing KILL "Great Outdoors" Set the Process Cache Size Whether a server request is for a cube (query processor) or report (report processor), the associated cube data must eventually be handled by a query processor. This is why the Maximum Processes setting (p. 33) for cubes is so vital for optimal server performance. Each instance of a query processor is allocated a memory cache that stores results previously retrieved from its associated cube. Using the cache, the process may generate results more quickly, because reusing results in a cache is faster than querying a cube again. When a cache is full, the results used least recently are discarded. By default, the memory cache is 8 MB on Windows and 16 MB on UNIX. You can increase the cache size to increase the probability that results are found in caches. However, there is a threshold at which the overhead of managing very large cache sizes outweighs any benefits gained from increasing the cache size. In addition, because all caches on a PowerPlay server are the same size, a large cache size can significantly impact memory resources of the server. For example, with a cache size of 16 MB, 12 processes require 192 MB (16 MB x 12) of available memory. Setting the optimal cache size can significantly improve performance, which means better response time for PowerPlay users. As a rule, the cache size should be 20% of your average cube size, and at most 32 MB. Some reasons for considering increasing the process cache size include • the average query (sec/Hit) time is too long • your typical cube size is large (greater than 10 MB) • monitoring your server shows that there is plenty of memory to spare • 80% of hits are on 20% of your cubes Steps for Windows 1. Open the file cern.ini in a text editor. It is located in the bin directory. 2. Locate or add the section [PowerPlay DataServer]. Enterprise Server Guide 35
- Page 1 and 2: COGNOS (R) Business Intelligence Se
- Page 3 and 4: Table of Contents Introduction 7 Ch
- Page 5 and 6: Chapter 6: Audit Server Activity 71
- Page 7 and 8: Introduction What Is in This Docume
- Page 9 and 10: Chapter 1: Enterprise Reporting Pow
- Page 11 and 12: Chapter 1: Enterprise Reporting •
- Page 13 and 14: Chapter 1: Enterprise Reporting Ser
- Page 15 and 16: Chapter 2: Configure Servers This c
- Page 17 and 18: Chapter 2: Configure Servers Daemon
- Page 19 and 20: Chapter 2: Configure Servers 2. Fro
- Page 21 and 22: Chapter 2: Configure Servers Securi
- Page 23 and 24: Chapter 2: Configure Servers Perfor
- Page 25 and 26: Disable Saving of Cognos Sub-Cubes
- Page 27 and 28: Chapter 3: Control Processes This c
- Page 29 and 30: Chapter 3: Control Processes In a m
- Page 31 and 32: Chapter 3: Control Processes Exampl
- Page 33: Monitor Windows Connections Chapter
- Page 37 and 38: Chapter 4: Deploy Cubes and Reports
- Page 39 and 40: Chapter 4: Deploy Cubes and Reports
- Page 41 and 42: Add a Cube or Report Chapter 4: Dep
- Page 43 and 44: Chapter 4: Deploy Cubes and Reports
- Page 45 and 46: Add Dimension Line Information to a
- Page 47 and 48: Chapter 4: Deploy Cubes and Reports
- Page 49 and 50: Chapter 4: Deploy Cubes and Reports
- Page 51 and 52: Chapter 4: Deploy Cubes and Reports
- Page 53 and 54: Chapter 4: Deploy Cubes and Reports
- Page 55 and 56: Chapter 4: Deploy Cubes and Reports
- Page 57 and 58: Chapter 4: Deploy Cubes and Reports
- Page 59 and 60: Chapter 4: Deploy Cubes and Reports
- Page 61 and 62: Chapter 5: Provide Drill-through Ac
- Page 63 and 64: Chapter 5: Provide Drill-through Ac
- Page 65 and 66: Chapter 5: Provide Drill-through Ac
- Page 67 and 68: Chapter 5: Provide Drill-through Ac
- Page 69 and 70: Chapter 5: Provide Drill-through Ac
- Page 71 and 72: Chapter 6: Audit Server Activity Us
- Page 73 and 74: Chapter 6: Audit Server Activity 2.
- Page 75 and 76: Chapter 6: Audit Server Activity Th
- Page 77 and 78: Chapter 6: Audit Server Activity Co
- Page 79 and 80: Level Usage Table Chapter 6: Audit
- Page 81 and 82: Appendix A: Context Help This secti
- Page 83 and 84: Appendix A: Context Help Maximum Re
Chapter 3: Control Processes<br />
When you stop the processing, the following dialog box appears.<br />
If you select Stop After all Requests Are Complete, the server stops accepting new requests,<br />
including any in the queue, but requests that are being processed continue until they are finished.<br />
You can monitor the processes in the Monitor tab of PowerPlay Enterprise - Server<br />
Administration. If you select Stop Immediately, the server stops processing requests.<br />
Steps<br />
1. In PowerPlay Enterprise - Server Administration, select an item.<br />
2. From the Actions menu, click Stop.<br />
3. Select one of the stop options.<br />
4. Click OK.<br />
Notes<br />
• Selecting a server and stopping it is not the same as shutting it down (p. 15), but rather like<br />
stopping the processes of an implied folder at the root level.<br />
• If you are using the ppadmtool in Windows or on UNIX, you can stop processes by typing<br />
KILL and then the object name; for example, you can stop processes against the Great<br />
Outdoors cube by typing<br />
KILL "Great Outdoors"<br />
Set the Process Cache Size<br />
Whether a server request is for a cube (query processor) or report (report processor), the<br />
associated cube data must eventually be handled by a query processor. This is why the Maximum<br />
Processes setting (p. 33) for cubes is so vital for optimal server performance.<br />
Each instance of a query processor is allocated a memory cache that stores results previously<br />
retrieved from its associated cube. Using the cache, the process may generate results more quickly,<br />
because reusing results in a cache is faster than querying a cube again. When a cache is full, the<br />
results used least recently are discarded.<br />
By default, the memory cache is 8 MB on Windows and 16 MB on UNIX. You can increase the<br />
cache size to increase the probability that results are found in caches. However, there is a<br />
threshold at which the overhead of managing very large cache sizes outweighs any benefits gained<br />
from increasing the cache size. In addition, because all caches on a PowerPlay server are the same<br />
size, a large cache size can significantly impact memory resources of the server. For example, with<br />
a cache size of 16 MB, 12 processes require 192 MB (16 MB x 12) of available memory.<br />
Setting the optimal cache size can significantly improve performance, which means better response<br />
time for PowerPlay users. As a rule, the cache size should be 20% of your average cube size, and<br />
at most 32 MB.<br />
Some reasons for considering increasing the process cache size include<br />
• the average query (sec/Hit) time is too long<br />
• your typical cube size is large (greater than 10 MB)<br />
• monitoring your server shows that there is plenty of memory to spare<br />
• 80% of hits are on 20% of your cubes<br />
Steps for Windows<br />
1. Open the file cern.ini in a text editor.<br />
It is located in the bin directory.<br />
2. Locate or add the section [PowerPlay DataServer].<br />
Enterprise Server Guide 35
Change language