The IT professionals occasionally fear that vRealize Infrastructure Navigator will impose an additional load on the production systems. vRealize Infrastructure Navigator typically is non-invasive and passively monitors performance traffic and captures data using the existing vSphere APIs, so it generally does not cause much load. With that said, similar to any monitoring tool, proper careful configuration and allocation of resources will reduce the overhead of the tool. The number of data points to save and the frequency of updating of graphs is another performance. What would your size advice be, as a result of experience?
