Event Throughput Performance
This chapter provides results of the performance tests for the Oracle Communications Unified Assurance microservice event pipeline, which involves Trap Collector to collect events, FCOM Processor to process events, and Event Sink to insert events into the Event database.
The testing was performed in a lab environment, which cannot exactly replicate a production environment. For example, in order to achieve repeatable testing, the pipeline in the lab environment did not include the SNMP Poller or RCA Availability Engine.
Although the Unified Assurance environment was configured as described in Unified Assurance Configuration, only the collection servers, Event database, and Historical database are relevant to this test.
Additional Configuration for Event Throughput Performance
In addition to the basic configuration described in Performance Test Configuration, the additional database tuning parameters listed in the following table were adjusted for the Event database during the test runs.
| Parameter | Value |
|---|---|
| max_connections | 200 |
| thread_cache_size | 250 |
| innodb_flush_log_at_trx_commit | 2 |
| innodb_log_buffer_size | 2G |
| innodb_thread_concurrency | 0 |
| innodb_buffer_pool_size | -- |
| innodb_redo_log_capacity | -- |
| innodb_read_io_threads | 16 |
| innodb_write_io_threads | 16 |
| innodb_io_capacity | 1000 |
| innodb_io_capacity_max | 20000 |
| transaction-isolation | READ-COMMITTED |
Results for Event Throughput Performance
In this scenario, 6,000 events were submitted per second for 2 hours.
The following table lists the results for the key performance metrics.
| Metric | Result |
|---|---|
| Throughput | 6,000 events per second |
| Events submitted | 43,200,001 |
| Events persisted to Event and Historical databases | 43,153,563 |
| Event loss | 0.11% |
| CPU usage: Collection | 2.92% (average of all collection servers) |
| Memory usage: Collection | 42.08% (average of all collection servers) |
| Disk space growth: Collection | 2.67% (average of all collection servers) |
| CPU usage: Event database | 2.29% |
| Memory usage: Event database | 7.72% |
| Disk space growth: Event database | 73 GB |
| CPU usage: Historical database | 13.9% (average of all Historical databases) |
| Memory usage: Historical database | 45.8% (average of all Historical databases) |
| Disk space growth: Historical database 1 | 17 GB (no growth for 2 and 3) |
| Historical database eventanalytics index growth | 15 GB |
| Historical database logs index growth | 381.8 MB |
| Synchronization delay | Less than 1 second |
| Average disk space per OpenSearch document | 422.99 bytes |
| Average mysql-bin file size increase per event record | 1,820.54 bytes |
Additionally, no growth was observed in the Event database ibdata file.