Maximum number of transactions

[bonsai]

※Paris version

When I checked the transactions when I executed the following script, I could only execute up to 8 transactions at a time.

function scripte() {
    //ScheduleJob

    sleepe(12000);

    function sleepe(a) {
        var startMsec = new Date();
        while (new Date() - startMsec < a);
    }
}
var sched = new ScheduleOnce();
sched.script = '(' + scripte + ')();';
sched.schedule();
sched.schedule();
sched.schedule();
sched.schedule();
sched.schedule();
sched.schedule();
sched.schedule();
sched.schedule();
sched.schedule();
sched.schedule();
sched.schedule();
sched.schedule();

Originally I want 12 transactions to be launched.
Can this be adjusted from 8 to 12?

[Tony Chatfield1]

Hi, I would not recommend any changes to worker\burst functionality unless you have an exceptionally good understanding of the platform, as changes of this nature may impact platform performance\responsiveness and also it's stability.

I have not seen documentation that covers off how an instance allocates individual jobs between nodes and their workers, but based on observations I think you may find that there is some attempt by the instance to allocate similar jobs to a node\worker, so that they are processed sequentially (and perhaps this is more efficient use of resource).

Perhaps you could explain why you need to execute multiple jobs on 1 table concurrently?
Even if these jobs started processing concurrently, the outcome IE updates to other tables, generation of other jobs, sysevents, notifications etc etc, would eventually end up in a sequential\queue somewhere...within the instance or externally.

[bonsai]

By the way, is the maximum number of concurrent executions 8 times for paid instances instead of free development instances?
Is there a difference such as an increase in the number of nodes that can be executed simultaneously in the case of a fee?

[Hitoshi Ozawa]

Following thread provides information on the standard ServiceNow instance. Anything beside the standard default should be discussed with ServiceNow sales reps instead of here.  I think it's all going to depend on money.

8 background schedules is the standard for ServiceNow paid production instance.

https://community.servicenow.com/community?id=community_question&sys_id=bb8c8fa5db9cdbc01dcaf3231f96...

[Hitoshi Ozawa]

The default is 8 background jobs per node. Customers can buy more nodes to increase number of concurrent background jobs.

Also, it's the total of 8 concurrent background jobs. Background jobs are not just jobs created by scheduler but other jobs such as Discovery, email processing, and workflow. That is, if some other such as those are running, there would be less than 8 user scheduled background jobs times number of nodes.

It's also "background" jobs. End users are still able to click on "Order"/"Submit" button and have the form processed while these background jobs are running.

Furthermore, 8 background jobs are the number set by ServiceNow. It's not the limitation set by Java container such as Tomcat.

Finally, if running database operations in a background job, there's also number of database connections.

There's a need to balance between foreground , background, and database to obtain a maximum throughput from an instance.

[Hitoshi Ozawa]

If performance is an issue and money isn't a problem, may be switch to using Oracle. The default is MySQL/MariaDB.

I've read several times about ServiceNow supporting Oracle database but I can't find the page right now.