3 Replies Latest reply on Nov 7, 2017 1:20 PM by Andrea Vasco

    TSCO Workload CPU needs to be reported in RAW numbers

    Doug Case
      Share This:

      BMC has chosen to normalize workload CPU utilization, which would be great if we didn't have thousands of hyper-threaded Intel servers.  Even if we had non-hyper-threaded servers, we still have instances when we want raw CPU utilization.  Our Hadoop cluster has 40 data nodes and 8 edge nodes (Each with 20 physical and 40 logical processors).  We have multiple workloads defined based on process IDs and we need to show the number of processors consumed across this environment by workload.  Since the tool is reporting CPU in a normalized number based on logical core count it is vastly understated.  I can export the data and do the math to get to raw, but that kind of defeats the purpose of automated trend reporting.       

        • 1. Re: TSCO Workload CPU needs to be reported in RAW numbers
          Mike West

          There are a couple ways to approach this within TSCO.

           

          The longer term approach is to create an Idea so that this could be evaluated by product management for roadmap.

           

          There are a couple options for short-term approach that you could consider:

           

          1. Assuming you want to mainly report the workloads in raw cores used, you can create a Formula and use the processor count from the server running the workload to derive the cores used by the workload.  This approach will allow you to build reports and present an analysis, but it would not allow you to build a forecast for the workload using cores used or derive any statistics.

           

          2. In case you want to also do a forecast or derive some statistics for the workload cores used, then you can create a self-ETL to produce custom metrics to contain the cores used by the workload.  You may be somewhat familiar with using the self-ETL as this was done to create effective CPU for hyper-threaded systems in your environment.

           

          These are some options.  However, if the actual goal was to get this on the roadmap, then you should repeat this request as an Idea for the TSCO product management team to review for roadmap.

           

          Best Regards,

           

          Mike West

          • 2. Re: TSCO Workload CPU needs to be reported in RAW numbers
            Doug Case

            Thanks Mike for the information.  I will submit an idea for future consideration.  As for the short term options we will look to try one of them.  I think this would be doable to recreate the data in raw unlike the Effective Rate ETL which we recently discovered is not the same as effective rate calculated in BPA/Visualizer data.  We need to discuss that. 

            • 3. Re: TSCO Workload CPU needs to be reported in RAW numbers

              Hey Doug, for sake of curiosity have you tried working it around using a formula? that may help de-normalize CPU utilization in a pretty automated fashion.