Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

significant increase in network and memory footprint after upgrading to 1.1.x from 1.0.x #1327

Closed
aylei opened this issue Dec 11, 2019 · 3 comments · Fixed by #1504
Closed
Assignees
Labels
needs-cherry-pick-1.1 type/bug Something isn't working type/question Further information is requested

Comments

@aylei
Copy link
Contributor

aylei commented Dec 11, 2019

Question

After upgrade tidb-operator from v1.0.3 to the latest master (a3f4b8d), there is a significant increase in network and memory footprint:

image
image

cluster scale:

  • Node: 60+
  • TiDB clusters: 70+
@aylei aylei added type/bug Something isn't working type/question Further information is requested labels Dec 11, 2019
@aylei aylei added this to the v1.1.0 milestone Dec 11, 2019
@aylei aylei self-assigned this Dec 11, 2019
@aylei
Copy link
Contributor Author

aylei commented Dec 11, 2019

image

@aylei
Copy link
Contributor Author

aylei commented Dec 11, 2019

The problem is introduced by ConfigMapInformer, we should remove the configmap cache.

Meanwhile, as @cofyc mentioned, cache for Secret has the same risk and should also be removed.

@github-actions
Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 15 days

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-cherry-pick-1.1 type/bug Something isn't working type/question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants