So is this the same as having a sub-pipeline and tune the pool size of the Pipeline execute?
This is in addition to this.
So if you have 100 documents, and only one pipeline execute with a pool size of 10, then 10 are distributed for each instantiation of execution.
In this case net instantiations are only 10.
Now with the same amount of documents, you have 2 routes each calling pipeline execute with a pool size of 10 then 50 are distributed in 2 routes and then 5 run across each instantiation of execution.
In this case net instantiations are now 20.
Hope that makes sense.
So then why I have such duplicate in terms of snap and why not just do one pipeline execute with pool size of 20?
It is basically distribution of load and to achieve greater performance.
You have to take into the snaplexes and nodes into account.
Suppose you have a large snaplogic environment with multiple snaplexes and multiple nodes, you can basically route this to different snaplexes and achieve greater performance.
With just one pipeline execute you cannot do that. They will be distributed to only one snaplex even though it has multiple nodes in it.
Ok, that makes sense then. Thanks!
