Scale Specifications

Cisco Spaces: Connector 3 use case and capacity details

This table outlines the three types of Cisco Spaces: Connector types, their use cases, and key scaling KPIs such as AP counts, client or tag counts, and outgoing message rates.

These are the key factors affecting scale:

  • Connector Message Rate Limitations:

    • The connector works only within outgoing message rate limits.

    • If the message rate limits are reached, the connector's ability to scale becomes restricted.

    • We recommend deploying within these limits to maintain system stability.

  • CPU Type Requirement: The type of CPU on the connector’s host server affects scale and performance.

  • Network Delays: High network latency reduces connector performance.

  • Device Filtering Requirement for IoT Service: To fully utilize the connector for IoT services, you must enable device filtering. For more information, see the Cisco Spaces: IoT Service Configuration Guide (Wireless).

This table suggests the scale configuration that are tested on VMware ESXi platform with Intel(R) Xeon(R) Platinum 8362 CPU.
Table 1. Connector types and scale configurations
Connector Type Use Case AP Count Client/Tag Count Connector Outgoing Message Rate

Standard

Location (NMSP) Only

9K

Client Count: 90K (Wireless Clients, RFIDs & Rogues)

21K NMSP msgs/sec

Advanced1

Location (NMSP) Only

15K

Client Count: 150K

38K NMSP msgs/sec

IoT Only

3K

BLE Tag Count: 25K

150K BLE msgs/sec

Location (NMSP) + IoT

12K(2K APs is doing IoT and location; 10K APs is doing only location)

Client Count: 100K

BLE Tag Count: 20K

17K NMSP msgs/sec

120K BLE msgs/sec

Advanced 2

Location (NMSP) Only

25K

Client Count: 250K (Wireless Clients, RFIDs & Rogues)

44K NMSP msgs/sec

IoT Only

4.5K

BLE Tag Count: 40K

220K BLE msgs/sec

Location (NMSP) + IoT

18K

(3K APs doing both IoT and Location; 15K APs is doing location only)

Client Count: 150K

BLE Tag Count: 30K

38K NMSP msgs/sec

170K BLE msgs/sec