How to estimate BOARD Client Occupancy Bandwidth

Document created by ggallo Employee on Jul 27, 2017
Version 1Show Document
  • View in full screen mode

Overview

The following can be used when in need of estimating BOARD Client occupancy bandwidth or when evaluating the Network capacity to sustain the Application.

The following benchmark guidelines are provided for a BOARD Windows Client based application.

 

Platform Specs

It is important to report the BOARD Speed Test of the different architecture elements: BOARD Server, BOARD Clients and Network.

Refer to Speed Test Performance: definition of parameters and BOARD functionalities for explanation

 

Test Cases

It is important to identify the Screens and Procedures that are more likely going to simulate the daily behavior of the Users: these will become our "test" for evaluating occupancy

It is important also to perform the actions and navigate the previously identified screens, using different Database Security and User profiles' mix (including the Administration Profile), to provide a more realistic scenario.

 

Sample Recap Table

ActionCapsuleScreen/Procedure
LoginNot ApplicableNot Applicable
Open CapsuleSales Budget00 - Main
Open ScreenSales BudgetAll
Refresh ScreenSales BudgetAll
Run ProcedureSales Budget00 – 01 Budget Init
Data EntrySales BudgetInput Budget Quantity
SelectorSales BudgetCustomer Channels
DrillDownSales BudgetFrom Customer to Product

 

The test cases identified, should be run n times, enough to identify a consistent and meaningful average data exchange.

The single benchmarks do not differ too much from the Average,  

 

 

Benchmark occupancy

During Test cases execution the following information should be monitored:

Data Size (KB): it reports the data traffic size of any information that flows between the BOARD Server and BOARD Client.  It must be tracked in

  • Download: data from BOARD Client to BOARD Server
  • Upload: data from BOARD Server to BOARD Client

 

Occupancy Bandwidth (KB/s): it reports the Occupancy Bandwidth of any information that flows between the BOARD Server and BOARD Client.  It must be tracked in

  • Download: data from BOARD Client to BOARD Server
  • Upload: data from BOARD Server to BOARD Client

 

Sample Report:

 

 

 

 

 

 

It is also important to Report the Benchmark Peaks

 

Concurrency Evaluation

If the Business Scenario includes a very high concurrency a linear growth can’t be adopted as an algorithm to estimate the Total Bandwidth Occupancy but different parameters must be considered:

  • Size Peak of any Action
  • Number of Contemporary Users executing the Action
  • User Activity (Action Execution) Frequency per Sec

The combined use of these three factors determines the Occupancy Bandwidth.

 

a          total occupancy bandwidth per action (upload plus download)

b          number of potential (worst scenario) users executing the action

c          execution frequency of the action per sec per single user

n          number of action that have been included in the benchmark

3 people found this helpful

Attachments

    Outcomes