This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Memory Usage for the Foglight main Launcher service

Hi,

Just noticing that the Foglight main launcher service is taking 50.2% CPU on the Windows 2012 server that I have it running on. Is this normal for it to be consuming so much CPU?

Thanks...

Parents
  • Hi Peter,

    It all depends on what cartridges you are running. Some cartridges utilize more CPU resources than others.

    You could try running this script via Script Console to get some insight:

    import com.quest.nitro.service.util.MBeanRef;

    import javax.management.ObjectName;

    def CartCostMon = new MBeanRef(ObjectName.getInstance("com.quest.nitro:service=CartridgeCostMonitor")).ref();

    return (CartCostMon.diagnosticSnapshotAsString());

     

    The result should look like this:

    ==================== Performance Cost Collector =========================

    Last reset CPU cost statictics at:2017-07-06 09:59:59 EDT

    ==================== Cartridge Cost Summary(CPU) =========================

    +---------------------------------+----------------------+------------+

    | Cartridge Name | Total Execution Time | Percentage |

    +---------------------------------+----------------------+------------+

    | Virtual-VMware | 186200328.20 ms | 67.77% |

    | VMware-Performance-Agent | 28549402.88 ms | 10.39% |

    | ContextNotAvailable | 24701934.91 ms | 8.99% |

    | CommonAnalytics | 10869328.61 ms | 3.96% |

    | Virtual-VMware-Base | 4720663.31 ms | 1.72% |

    | DB_SQL_Server | 3010228.37 ms | 1.10% |

    | Virtual-VMware-Intelliprofile | 1721932.74 ms | 0.63% |

    Once you know what cartridge is using high CPU, you could contact Support and check if this is normal or not.

    I hope this helps,

    Regards,

    Gaston.

Reply
  • Hi Peter,

    It all depends on what cartridges you are running. Some cartridges utilize more CPU resources than others.

    You could try running this script via Script Console to get some insight:

    import com.quest.nitro.service.util.MBeanRef;

    import javax.management.ObjectName;

    def CartCostMon = new MBeanRef(ObjectName.getInstance("com.quest.nitro:service=CartridgeCostMonitor")).ref();

    return (CartCostMon.diagnosticSnapshotAsString());

     

    The result should look like this:

    ==================== Performance Cost Collector =========================

    Last reset CPU cost statictics at:2017-07-06 09:59:59 EDT

    ==================== Cartridge Cost Summary(CPU) =========================

    +---------------------------------+----------------------+------------+

    | Cartridge Name | Total Execution Time | Percentage |

    +---------------------------------+----------------------+------------+

    | Virtual-VMware | 186200328.20 ms | 67.77% |

    | VMware-Performance-Agent | 28549402.88 ms | 10.39% |

    | ContextNotAvailable | 24701934.91 ms | 8.99% |

    | CommonAnalytics | 10869328.61 ms | 3.96% |

    | Virtual-VMware-Base | 4720663.31 ms | 1.72% |

    | DB_SQL_Server | 3010228.37 ms | 1.10% |

    | Virtual-VMware-Intelliprofile | 1721932.74 ms | 0.63% |

    Once you know what cartridge is using high CPU, you could contact Support and check if this is normal or not.

    I hope this helps,

    Regards,

    Gaston.

Children
No Data