blob: 8e0aa22ba452345a5945d6501c2b24601494ab2b (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
|
---
title: "VPP Performance"
weight: 1
---
# CSIT 24.06 - VPP Performance
1. TEST FRAMEWORK
- **CSIT test environment** version has been updated to ver. 15, see
[Environment Versioning]({{< ref "../../../infrastructure/fdio_csit_testbed_versioning" >}}).
- **General Code Housekeeping**: Ongoing code optimizations and bug fixes.
2. VPP PERFORMANCE TESTS
- No updates.
3. PRESENTATION AND ANALYTICS LAYER
- Detailed views added to comparison tables.
# Known Issues
These are issues that cause test failures or otherwise limit usefulness of CSIT
testing.
## New
Any issue listed here may have been present also in a previous release,
but was not detected/recognized/reported enough back then.
Also, issues previously thought fixed but now reopened are listed here.
**#** | **JiraID** | **Issue Description**
------|--------------------------------------------------|--------------------------------------------------------------
1 | |
## Previous
Issues reported in previous releases which still affect the current results.
**#** | **JiraID** | **Issue Description**
------|--------------------------------------------------|--------------------------------------------------------------
1 | |
## Fixed
Issues reported in previous releases which were fixed in this release:
**#** | **JiraID** | **Issue Description**
------|--------------------------------------------------|--------------------------------------------------------------
1 | |
# Root Cause Analysis for Regressions
List of RCAs in CSIT 24.06 for VPP performance regressions.
Not listing differences caused by known issues (uneven worker load
due to randomized RSS or other per-worker issues).
Also not listing tests which historically show large performance variance.
Contrary to issues, these genuine regressions do not limit usefulness
of CSIT testing. So even if they are not fixed
(e.g. when the regression is an expected consequence of added functionality),
they will not be re-listed in the next release report.
**#** | **JiraID** | **Issue Description**
------|--------------------------------------------------|--------------------------------------------------------------
1 | |
|
