Amarisoft

Factors on MS/s in [t cpu] output

This page is not about testing anything. This is more of information purpose. This is about factors affecting (determining) the MS/s column value of t cput output. (NOTE : Regarding t cpu output, TX/RX diff would be the most commonly referenced information. Regarding TX/RX diff, refer to this wiki ). The main purpose of this page is to show how to help you to figure out those values for the specific configuration that you are using for a specific test. It is impossible to provide all the possible values in this page because it varies depending on various factors like RAT type, number of Cells, Bandwidth, sample rate of each sdr card etc. From the examples shared in this page, try to get some big picture and learn how to figure out the exact values for your own configuration.

NOTE : MS/s indicates the aggregated sample rate of all the cells that are configured in your configuration.

Info t cpu sample about 01

NOTE : CPU % is not the main topic in this page... but as a generic comments, you may assume that the CPU % would vary the user data rate to be processed. So it varies dynamically depending onfactors like idle and connected call status, bandwidth, number of carriers, tdd ul/dl config (in case of TDD)etc. It is perfectly normal if you have CPU% higher than100%. When more than 1 CPU core are being used, you would see CPU% higher than 100% (e.g, over 100% when 2 CPU core areused, over 200% if 3 CPU are used etc)

Table of Contents

Introduction

In modern wireless communication systems, performance monitoring and analysis are critical for optimizing network efficiency and ensuring quality of service. One essential metric in this context is the MS/s (Mega Samples per second) column value, typically observed in the t cput output. This value represents the aggregated sample rate across all configured cells, directly correlating to the data throughput and processing demands placed on the underlying hardware. The calculation and interpretation of MS/s are influenced by multiple technical factors, including Radio Access Technology (RAT) type (such as LTE, NR, etc.), the number of cells, channel bandwidths, and the sample rate settings of individual Software Defined Radio (SDR) cards. Since each deployment scenario presents unique configurations, there is no universal MS/s value; instead, it must be deduced based on the specific test environment and hardware setup. Understanding these factors is crucial for engineers and network administrators aiming to evaluate system performance, especially in the context of TX/RX (transmit/receive) differentials and their relationship to traffic load and resource allocation. While CPU utilization percentage is a secondary consideration here, it is important to note that it fluctuates with varying data loads, connection statuses, and configurations—occasionally exceeding 100% in multi-core systems. This page is designed to provide in-depth information and practical guidance on interpreting and determining MS/s values for your specific configuration, empowering you to extrapolate and apply these concepts to diverse testing and deployment scenarios.

Summary of the Tutorial

This tutorial describes the procedures for testing various configurations of Software Defined Radio (SDR) cards in a Callbox Classic setup. Multiple test scenarios are covered, focusing on LTE and NR SA/NSA bandwidths and MIMO configurations.

The tutorial provides an overview of the test procedures and highlights the importance of matching hardware and configuration settings to achieve valid results for each scenario.

SDR Card

I have 4 sdr cards on my Callbox (Callbox Classic) as shown below (You can get these information for your setup, by running ./sdr_util -c all version in /root/trx_sdr).

Info t cpu sample SDRcards 01

Info t cpu sample SDRcards 02

LTE BW 5Mhz, SISO

Info t cpu sample LTE BW5 SISO 01

Info t cpu sample LTE BW5 SISO 02

LTE BW 20Mhz, SISO

Info t cpu sample LTE BW20 SISO 01

Info t cpu sample LTE BW20 SISO 02

LTE 20Mhz, 2x2 MIMO

Info t cpu sample LTE BW20 2x2 01

Info t cpu sample LTE BW20 2x2 02

NR SA 20Mhz, 2x2 MIMO

Info t cpu sample NR SA BW20 2x2 01

Info t cpu sample NR SA BW20 2x2 02

NR SA 40Mhz, 2x2 MIMO

Info t cpu sample NR SA BW40 2x2 01

Info t cpu sample NR SA BW40 2x2 02

NR SA 50Mhz, 2x2 MIMO

Info t cpu sample NR SA BW50 2x2 01

Info t cpu sample NR SA BW50 2x2 02

NR SA 100Mhz, 2x2 MIMO

I tested SA 100Mhz 2x2 using 2 x SDR50 cards and with the sample rate as shown below. If you are using SDR100 and using different sample_rate, you may get different result.

Info t cpu sample NR SA BW100 2x2 01

Info t cpu sample NR SA BW100 2x2 02

Info t cpu sample NR SA BW100 2x2 03

NR NSA 20+100Mhz, SISO

I tested SA 100Mhz 2x2 using 2 x SDR50 cards and with the sample rate as shown below. If you are using SDR100 and using different sample_rate, you may get different result.

Info t cpu sample NR NSA BW 20 100 SISO 01

Info t cpu sample NR NSA BW 20 100 SISO 02

Info t cpu sample NR NSA BW 20 100 SISO 03