Hi, There is no such thing as normal job. All jobs are normal but can run in different run-time modes. They all go to a queue first unless the schedule type is [on scheduler startup]. In the docs you can find full description of these run-time modes including graphical flow charts and diagrams demonstrating how this all works. I don't have anything to add here. Queue size has nothing to do with memory. It simply limits how many jobs can pile up in a queue before the queue suspends adding new jobs. This is simply to prevent uncontrolled queue growth (1 job get stuck and the rest gets never executed). The size limits how much disk storage is used to store queued job definitions (don't confuse that with job definitions stored in the job databases) Queue is more like a logical concept then a physical object. Async. jobs require more resources ~1-2 MB per job as the scheduler need to create a separate monitoring and processing threads for these jobs. Of course extra possessing threads create more load for the server. When the number of executing jobs is relatively small this it is all irrelevant. Number of queues – this really depends on how many you need. Normally you should assign different applications (job streams) to different queues and set these jobs to run synchronous. Queues allow you to separate different applications logically and run them independently. Shall you need to link them and run consequently, you can use the job dependencies feature for that. Definitely a job that runs every minute should be set to run in sync. mode to relax system load or even better convert it to a async job script that starts on startup and runs in the background forever. The script could have a never-ending loop with waits between job condition checks and between actions. There then will be only one job instance and one processing thread – which is much more efficient. : Hi, : Problem
: ----------------------------
: We have a job that runs every minute. Should we schedule it as a detached job
: in a queue or should we schedule it a normal job and create a separate
: queue
: or should we run it as a async job. : Questions
: -------------------------------- : I want to know the exact differences and uses of the three different types of
: jobs that we have. : Normal Job -- Standard Queued Job
: Detached Job -- Does this use the queues resources. Simply put if this job
: were running would it block another job running in the same queue
: Async Job -- Help "says" uses more resources. How much more
: resources does it use and what is the target usage : How may jobs can be scheduled in a queue? When we say that each queue uses 4
: MB of Virtual memory, does it mean 4 MB of RAM or something else.
: How many queues should be created on a 24X7 scheduler. : 1 MB of queue space -- how many jobs can be allocated. : Thank you, : Soumitra
|
