You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
After installing the operator and launching a DB the memory usage spiked to 13GB before any connections were made to the DB.
The memory usage is from MysqlD running inside a Kind k8s cluster on my local machine.
Here's a snapshot of the memory using prometheus within Lens
What you expected to happen:
After installation the pod tends to consume negligible memory. Around 200MB at idle. Even after a few thousand rows are added we don't normally see more than 300MB memory usage within k8s.
How to reproduce it (as minimally and precisely as possible):
Environment:
Fedora 35
Docker
Kind
Prometheus
Lens for monitoring
Set up Kubernetes IN Docker (KIND) https://kind.sigs.k8s.io/
Install bitpoke mysql operator v0.6.2
Create the following DB:
What happened:
After installing the operator and launching a DB the memory usage spiked to 13GB before any connections were made to the DB.
The memory usage is from MysqlD running inside a Kind k8s cluster on my local machine.
Here's a snapshot of the memory using prometheus within Lens
What you expected to happen:
After installation the pod tends to consume negligible memory. Around 200MB at idle. Even after a few thousand rows are added we don't normally see more than 300MB memory usage within k8s.
How to reproduce it (as minimally and precisely as possible):
Environment:
Fedora 35
Docker
Kind
Prometheus
Lens for monitoring
Set up Kubernetes IN Docker (KIND)
https://kind.sigs.k8s.io/
Install bitpoke mysql operator v0.6.2
Create the following DB:
Watch memory usage.
The text was updated successfully, but these errors were encountered: