Hide Forgot
OpenShift 4.6 is migrating to (a default) of golang 1.15. Does this have any performance implications? We want to understand if golang 1.15 introduces any performance regression. We can do the following: - a simple test (maybe as simple as configmap create/update/get/delete), no pods churning so it does not need additional worker nodes. - setup a cluster with latest 4.5 rc, run the test and establish a baseline. - run the same test on 4.6 cluster, compare etcd/apiserver performance. check if there is any regression. We can use the following test - https://github.com/tkashem/graceful/blob/master/cmd/loader/main.go
Summary of the test results are captured here: https://hackmd.io/AG-8e7mgTv2Tgf-vyFMbag?edit. No noticeable performance regression detected at the specified apiserver load and test workload.
Per comment 1, we no need more performance tests for verification, just do below tests like description mentioned, - a simple test (maybe as simple as configmap create/update/get/delete), no pods churning so it does not need additional worker nodes. $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.6.0-0.nightly-2020-10-09-224055 True False 157m Cluster version is 4.6.0-0.nightly-2020-10-09-224055 $ oc create configmap special-config --from-literal=special.how=very --from-literal=special.type=charm configmap/special-config created $ oc get configmaps special-config -o yaml apiVersion: v1 data: special.how: very special.type: charm kind: ConfigMap metadata: creationTimestamp: "2020-10-10T04:40:46Z" managedFields: - apiVersion: v1 fieldsType: FieldsV1 fieldsV1: f:data: .: {} f:special.how: {} f:special.type: {} manager: oc operation: Update time: "2020-10-10T04:40:46Z" name: special-config namespace: default resourceVersion: "73990" selfLink: /api/v1/namespaces/default/configmaps/special-config uid: daa66863-bc85-4fae-8e45-f5d9ff86193b Add one new field, $ oc edit configmaps special-config configmap/special-config edited $ oc get configmaps special-config -o yaml apiVersion: v1 data: special.how: very special.type: charm kind: ConfigMap metadata: creationTimestamp: "2020-10-10T04:40:46Z" managedFields: - apiVersion: v1 fieldsType: FieldsV1 fieldsV1: f:data: .: {} f:special.how: {} f:special.type: {} f:special.what: {} manager: oc operation: Update time: "2020-10-10T04:40:46Z" name: special-config namespace: default resourceVersion: "74185" selfLink: /api/v1/namespaces/default/configmaps/special-config uid: daa66863-bc85-4fae-8e45-f5d9ff86193b $ oc delete configmaps special-config configmap "special-config" deleted $ oc get configmaps special-config Error from server (NotFound): configmaps "special-config" not found Cluster works as expected, so move the bug VERIFIED.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196