Profiles
Warning: The feature is currently available in the channel
8.0/candidateonly (revision 186+) and will be released to the channel8.0/stablesoon.
Charmed MySQL resource utilization depends on the chosen profile:
juju deploy mysql --config profile=testing
Profile values
| Value | Description | Tech details |
|---|---|---|
production(default) |
Maximum performance | ~75% of unit memory granted for MySQL max_connections=RAM/12MiB (max safe value) |
testing |
Minimal resource usage | innodb_buffer_pool_size = 20MB innodb_buffer_pool_chunk_size=1MB group_replication_message_cache_size=128MB max_connections=100 performance-schema-instrument=‘memory/%=OFF’ |
Config change
Note: Pre-deployed application profile change is planned but currently is NOT supported.
To change the profile, use juju config (see all charm configs):
juju deploy mysql --config profile=testing && \
juju config mysql profile=production
Juju Constraints
Juju constraints allows RAM/CPU limits for Juju units:
juju deploy mysql --constraints cores=8 mem=16G
Juju constraints can be used together with charm profile:
juju deploy mysql --constraints cores=8 mem=16G --config profile=testing