Scramble GT is uses multiple processors to update the logical system names considerably faster. It does not hang on to database cursors which can often slow down the standard transactions, as each update to the database is done independently of each other. Too many concurrent updates to the same database table could trigger database deadlocks. To avoid this as much as possible, Scramble GT randomizes the sequence of database table update requests. However, it is still possible that concurrent updates occur and this is acceptable up to a certain number of parallel processes.

The actual maximum amount of processors you can use on your system is dependent upon the capacity of the underlying database. It is recommended that you start the transaction with a smaller number of processes (e.g. 4-5) and then gradually increase the processing capacity if required. Please refer to the following section on how to achieve this.


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment