Just because the way, how XG logs the traffic is somehow different.
The module, which is involved to log the traffic, is another module, so basically it will simply involve another module, which has no high priority in the CPU handling.
Just because the way, how XG logs the traffic is somehow different.
The module, which is involved to log the traffic, is another module, so basically it will simply involve another module, which has no high priority in the CPU handling.
In very large environments, it may be possible that it affects performance if you are hitting disk read/write limits. In general - its hard to do since there are built in safeguards for this.
