![]() The scheduling policy in a system must attempt to satisfy two conflicting goals: fast process response time (low latency) and maximal system utilization (high throughput). A good example of this is a word processor, which normally sits waiting for key presses but at any moment might peg the processor in a rabid fit of spell checking. Other processes may be I/O-bound but dive into periods of intense processor action. Processes can exhibit both behaviors simultaneously: The X Window server, for example, is both processor-intense and I/O-intense. Of course, these classifications are not mutually exclusive. ![]() The ultimate example of a processor-bound process is one executing an infinite loop. A scheduler policy for processor-bound processes, therefore, tends to run such processes less frequently but (optimally, to them) for longer durations. Because they are not I/O-driven, however, system response does not dictate that the scheduler run them often. They tend to run until they are preempted because they do not block on I/O requests very often. Consequently, such a process is often runnable, but for only short durations because it will eventually block waiting on more I/O (this is any type of I/O, such as keyboard activity, and not just disk I/O).Ĭonversely, processor-bound processes spend much of their time executing code. The former is characterized as a process that spends much of its time submitting and waiting on I/O requests. Processes can be classified as either I/O-bound or processor-bound. I/O-Bound Versus Processor-Bound Processes A scheduler's policy often determines the overall feel of a system and is responsible for optimally utilizing processor time. If you deploy multiple real-time aggregations (RTA) for one or more activities, you have the option to specify a different time window for each RTA.Policy is the behavior of the scheduler that determines what runs when. Modify the RTATimeSlice values, located in the bam_Metadata_Activities table in the BAMPrimaryImport database. To change the TimeSlice value in the BAM_Metadata_Activities table To change the TimeSlice value in the BAM Configuration fileĬhange the value in this line of the BAM Configuration file: 5 ![]() If you set the value of the TimeSlice property to five minutes, instance A and instance B are grouped together. Instance B is completed and persisted in the BAM primary import database at 1:04 a.m. The TimeSlice property uses time that the data is written to the BAM primary import database to group BAM instance data.įor example, instance A is completed and persisted in the BAM primary import database at 1:02 a.m. You use the TimeSlice property to group completed BAM instance data. If you want to change the TimeWindow and TimeSlice values without undeploying the BAM infrastructure, you can modifying the columns in the BAM_Metadata_Activities table in the BAM primary import database. For information about deploying a BAM definition, see How to Deploy BAM Definitions. To enact the changes they make in the BAM configuration file, administrators must undeploy the current BAM configuration, and then deploy the updated BAMConfiguration.xml.įor information about undeploying a BAM definition, see How to Remove BAM Definitions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |