Database job- load/cost for database

Question

How much database gets slower when new Jobs are created in database?
I understand that Job is a kind of Timer that database engine needs to run and it is a kind of loop which check weather the schedule time has arrived now or not to run some code. So this loop may make database slower i think. But not much i guess?
I have very busy/loaded database and i don't want to make database more slower. I thought maybe i should to cron-job on the operating system level, so that database wont get mor load/work with bothering Job' handling.

Answer 1

CharlesRoos wrote:
How much database gets slower when new Jobs are created in database?That depends on a number of factors. Creating a job is a simply SQL UPDATE of the SYS.JOB$ table - and even a basic Oracle instance is capable of 1000's of updates per second.
I understand that Job is a kind of Timer that database engine needs to run and it is a kind of loop which check weather the schedule time has arrived now or not to run some code. So this loop may make database slower i think. But not much i guess?Not really. There is no timer as such. There are specific Oracle background processes that runs jobs - these deal with the work (job load) specified in the job table.
I have very busy/loaded database and i don't want to make database more slower. I thought maybe i should to cron-job on the operating system level, so that database wont get mor load/work with bothering Job' handling.Would be a silly waste of time. (whether an Oracle work load is run via cron using a dedicated server process, or by an Oracle job process - that workload is the same and needs running)