The requested behavior will not be possible. but we can look into the issue why CMDBOutput step throughput is very slow.

please check if you have followed the below recommendation if now can you create a support ticket so we can have look.

Things to take when running AI for large volumes of Data where Source Data is > 100K.

Bare Minimum Hardware:

OS:64 bit

CPU: 4

RAM: 8 GB

JVM: 64 bit.

It is strongly recommended that 32 bit systems are not used for running large integrations (>250K CIs). The best practices to run integrations are on a separate box with 64 bit hardware and operating system as specified above.

Configuration changes on the Plugin:

1> Initial loads where we are inserting data for the first time in CMDB, we can optimize performance by selecting options:a> Insert Always (Provided data in source is Unique) b> Select Cache Required option.

Cache size default is 1M that needs to be changed to 4M if the volume of data is about 2-4M.

2> For incremental loads one has to disable Insert Always option so that the modified records are updated appropriately.

3> Number of threads on the CMDBOutput plugin should not exceed 10. For smaller sized machines, use a lower number.

4> Number of threads on CMDBLookUp plugin should always be set to 1.

5> Carte server should be run with JVM options of -Xmx and -Xms set to 4096m.

6> If run from Spoon always run the Transformatin/Job with Logging mode set to Minimal. In Carte, it would be good to have logging disabled???? what is the default?

7> For Relationships as an best practise we can always turn of Updates.

Any Input Step will not pass the previous Step data to next one.it only pass the current data which it fetched based on the qualification.

Lookup - step will only check for the existence of CI in specific class depending on the keys mentioned in the look up values if the record with specific key values are found it will then return the attributes

With this approach overall I don't think the performance will improve . My suggestion use the same behavior as it is with CMDBOutput I am sure that give much more performance if you follow the best practice which I have suggested.

I can tell you the DB Tuning part also. because we have seen a good performance with CMDBOutput.

using ARInput and AROutput on the class level you may see a better performance but at the relationship side i don't think so.

have you tried the above recommendation to improve the CMDBOutput Plug-in whether that is resolved your issue are still you are seeing the same throughput 6 CI per sec. if yes can you create a support ticket so we can have a look.