6fusion Analytics
  • Overview
  • Introduction
    • What is 6fusion?
    • Not just another monitoring platform!
    • 6fusion's proposition to Organizations?
      • 6fusion Architecture
      • Consumption Financing
      • FASB Rules vs Balance Sheet
    • What's New
    • Getting Started
      • Planner Tool
      • 30-Day Historic Data Collection
      • Collector Installation Summary
  • 6fusion Guides
  • Collectors
    • Spot Meter for VMware Guide
    • Collector Installation for vCenter Guide
    • Setting vCenter Stat Levels
  • Planner Tool Guide
    • Enter the Workload Profile
    • Enter the Infrastructure Profile
    • Enter the Constraints
    • Understanding Consumption
    • Understanding your Costs
    • Key Resource Constraints
    • Machine and Resource Max
    • Capacity PIE Chart
    • Cores Utilization Chart
    • Resources Utilization Chart
    • Advanced Planner Input
    • Advanced Planner Report
  • Chargeback Reporting
Powered by GitBook
On this page

Was this helpful?

  1. Planner Tool Guide

Understanding Consumption

PreviousEnter the ConstraintsNextUnderstanding your Costs

Last updated 5 years ago

Was this helpful?

Infrastructure Results - Part 1. Various Consumption Levels

The first 4 sections in the results column can be described as follows:

  • @Current - This represents the current level of consumption based upon the workload profile, the infrastructure profile and the constraints you entered in the Inputs area

  • @Target - This represents the @MAX level less the Reserve % you set - thus becoming the available level or Target amount of consumption you can have before using up any of your reserve resources

@Target Note: This is also where you can quickly see how much is left UNUSED by %, this something you will want to keep track of and this represents the level of inefficiency present

  • @Max - This represents the maximum level of consumption you can have before ANY of your individual resources get consumed at 100% usage, thus creating your first resource bottleneck

  • @Theoretical - This represents the total consumption you can have if you used up 100% of ALL individual resources at the SAME TIME

@Theoretical Note: This is usually not possible, cause action is normally taken when any single resource hits 100%, thus creating a resource bottleneck and restricting continued usage of the remaining resources