It would be really easier if the cemperfdb site would be reachable.
The thing with the TIM is that depending on
- the traffic quality (TAP is best, RSPAN and VMs are worst)
- The type of traffic to Monitor (webservices/xml SOAP is worst, regular HTTP is best)
- encrypted/Not encrypted: HTTPS poses a 10% to 20% impact depending on the traffic quality and encryption type used
- the complexity of the monitored transactions (how many parameters are monitored, are response transaction definitions monitored)
- the use of Regular expressions in the transaction definitions (cost a lot)
- System the TIM runs on. VM apply an impact of 10%, if the resources for the TIM are reserved. If the resource configuration has not been reserved, the impact can be far greater.
- Java plugins in use. The impact can be huge if badly programmed.
On a general rule, a regular TIM will handle 100Mbps of HTTPS traffic and up to 120Mbps HTTP traffic on a clean network tap based data feed.
Assuming the traffic is regular, and that none of the negative impact "feature" as listed before is active.
I have attached here a Percentile distribution of current performance data on TIMs I have.
Please remember, these are value extracted from real running TIMs, and that the throughput values are raw throughput (means, data thrown at the TIMs before the filter come into action).
If you would send me a data-set (GitHub - CA-APM/cem-healthcheck-scripts: Provides scripts to collect data for troubleshooting an APM 9.x or later instal… - please get me a CEMPERF performance data run), I could juxtapose it to the currently known TIM data I have to see how loaded/charged your current TIMs are.
Note, for the previous graph, take the following into account: