24x7 slow to load jobs via 24x7 /SCRIPT

When I load job descriptions via 24x7 /SCRIPT jobs.jdl, I see that
the first jobs are entered at a speed of several per second, but
after 150 jobs or so, it takes several seconds for each job. I'm
not sure whether this is caused by GUI updates, or by the data
structures used internally in 24x7.

I have also tried doing this without the GUI active (i.e, with
just the service running), but that didn't seem to work (no sign
of the jobs later).

The /SCRIPT option could be made a lot more helpful - as it is, it
does not indicate whether the command works or not, and does not
give any hint as to what the problem is.

This is caused by the size of the job DB file. More jobs you have more time it takes to encrypt the file after each change.

: When I load job descriptions via 24x7 /SCRIPT jobs.jdl, I see that
: the first jobs are entered at a speed of several per second, but
: after 150 jobs or so, it takes several seconds for each job. I'm
: not sure whether this is caused by GUI updates, or by the data
: structures used internally in 24x7.

: I have also tried doing this without the GUI active (i.e, with
: just the service running), but that didn't seem to work (no sign
: of the jobs later).

: The /SCRIPT option could be made a lot more helpful - as it is, it
: does not indicate whether the command works or not, and does not
: give any hint as to what the problem is.

: This is caused by the size of the job DB file. More jobs you have more time
: it takes to encrypt the file after each change.

I see that having just a single SAV at the end of the file is much more efficient
than putting SAV after each job in the JDL file... does that sound correct?

I am not really sure. In old days "save" was required to commit all changes. In latest versions I think save if automatic after each change. But don't trust me on that. Please try moving SAV to the end and see if that makes a difference.

: I see that having just a single SAV at the end of the file is much more
: efficient
: than putting SAV after each job in the JDL file... does that sound correct?