List and briefly explain the rules for prioritising jobs
Answers
Answered by
0
Job priority defines the order in which jobs are processed. Jobs are usually executed as first-come, first-served. However, your system probably has certain jobs that need to be processed before other jobs.
Job priority does not affect the amount of resources a job gets once it is submitted to the data warehouse. Rather, it determines whether certain jobs are submitted to the data warehouse before other jobs in the queue.
For example, an executive in your company runs reports at unplanned times and you want to ensure that these reports are immediately processed. If no priority is set for the executive’s reports, they are processed with the other jobs in the system. Depending on data warehouse activity, this may require some wait time. If you assign a high priority to all jobs from the executive’s user group, Intelligence Server processes and submits those jobs to the data warehouse first, rather than waiting for other jobs to finish.
Intelligence Server processes a job on a database connection that corresponds to the job’s priority. If no priority is specified for a job, Intelligence Server processes the job on a low-priority connection. For example, jobs with high priority are processed by high-priority connections, and jobs with low or no priority are processed by a low-priority connection. For information about setting database connection thread priority, see Managing database connection threads.
Intelligence Server also engages in connection borrowing when processing jobs. Connection borrowing occurs when Intelligence Server executes a job on a lower priority connection because no connections that correspond to the job’s priority are available at execution time. High-priority jobs can run on high-, medium-, and low-priority connections. Likewise, medium-priority jobs can run on medium- and low-priority connections.
When a job is submitted and no connections are available to process it, either with the same priority or with a lower priority, Intelligence Server places the job in queue and then processes it when a connection becomes available.
You can set jobs to be high, medium, or low priority, by one or more of the following variables:
•Request type: Report requests and element requests can have different priority (Prioritizing jobs by request type).•Application type: Jobs submitted from different MicroStrategy applications, such as Developer, Scheduler, MicroStrategy Web, or Narrowcast Server, are processed according to the priority that you specify (Prioritizing jobs by MicroStrategy application type).•User group: Jobs submitted by users in the groups you select are processed according to the priority that you specify (Prioritizing jobs by user group).•Cost: Jobs with a higher resource cost are processed according to the priority that you specify (Prioritizing jobs by report cost). Job cost is an arbitrary value you can assign to a report that represents the resources used to process that job.•Project: Jobs submitted from different projects are processed according to the priority that you specify (Prioritizing jobs by project).
These variables allow you to create sophisticated rules for which job requests are processed first. For example, you could specify that any element requests are high priority, any requests from your test project are low priority, and any requests from users in the Developers group are medium priority.
A job is processed at the highest priority assigned to it by any rules. For example, if you set all jobs from your test project at low priority, and all jobs from users in the Developers group at medium priority, jobs in the test project that are requested by users in the Developers group are processed at medium priority.
Job priority does not affect the amount of resources a job gets once it is submitted to the data warehouse. Rather, it determines whether certain jobs are submitted to the data warehouse before other jobs in the queue.
For example, an executive in your company runs reports at unplanned times and you want to ensure that these reports are immediately processed. If no priority is set for the executive’s reports, they are processed with the other jobs in the system. Depending on data warehouse activity, this may require some wait time. If you assign a high priority to all jobs from the executive’s user group, Intelligence Server processes and submits those jobs to the data warehouse first, rather than waiting for other jobs to finish.
Intelligence Server processes a job on a database connection that corresponds to the job’s priority. If no priority is specified for a job, Intelligence Server processes the job on a low-priority connection. For example, jobs with high priority are processed by high-priority connections, and jobs with low or no priority are processed by a low-priority connection. For information about setting database connection thread priority, see Managing database connection threads.
Intelligence Server also engages in connection borrowing when processing jobs. Connection borrowing occurs when Intelligence Server executes a job on a lower priority connection because no connections that correspond to the job’s priority are available at execution time. High-priority jobs can run on high-, medium-, and low-priority connections. Likewise, medium-priority jobs can run on medium- and low-priority connections.
When a job is submitted and no connections are available to process it, either with the same priority or with a lower priority, Intelligence Server places the job in queue and then processes it when a connection becomes available.
You can set jobs to be high, medium, or low priority, by one or more of the following variables:
•Request type: Report requests and element requests can have different priority (Prioritizing jobs by request type).•Application type: Jobs submitted from different MicroStrategy applications, such as Developer, Scheduler, MicroStrategy Web, or Narrowcast Server, are processed according to the priority that you specify (Prioritizing jobs by MicroStrategy application type).•User group: Jobs submitted by users in the groups you select are processed according to the priority that you specify (Prioritizing jobs by user group).•Cost: Jobs with a higher resource cost are processed according to the priority that you specify (Prioritizing jobs by report cost). Job cost is an arbitrary value you can assign to a report that represents the resources used to process that job.•Project: Jobs submitted from different projects are processed according to the priority that you specify (Prioritizing jobs by project).
These variables allow you to create sophisticated rules for which job requests are processed first. For example, you could specify that any element requests are high priority, any requests from your test project are low priority, and any requests from users in the Developers group are medium priority.
A job is processed at the highest priority assigned to it by any rules. For example, if you set all jobs from your test project at low priority, and all jobs from users in the Developers group at medium priority, jobs in the test project that are requested by users in the Developers group are processed at medium priority.
Similar questions