This is something related to designing. I believe this needs to be discussed through a call to understand the exact scenario you are covering here. I would suggest you to open a case with Informatica support to have a detailed discussion on this.
The Matching process is the CPU intensive process. The searching,matching and sorting is taken care in the memory and the matching process is the most expensive and cpu intensive process.
Hope this helps.
I am not at all sure that opening a call with Informatica is applicable here. I am asking the question because I am trying to understand the recommendation from the FAQs here.
Basically, if you can have 2 scenarios: source data for IDTs in the same physical database as where the matching queries originate from (which I suspect is less common a pattern) and source data for IDTs is in a different database. When the FAQs talk about IIR being on the same server, that's ambiguous in this scenario, so I'm trying to clarify it.
ALso, unless I am misunderstanding, given how CPU-intensive matching is, it would seem like having IIR on a separate server from either database so not to keep spiking the DB CPU would be more advantageous. So what am I missing?