How to set more memory to use?

Redis Object Cache will use as much as possible. Maybe your dataset is small, or your maxttl is evicting too fast.

Thanks alot, i will check that, as both domains should use the same Redis Config i was just wondering, if i have maybe to set something else in per domain setting. As one always shows so much ram used and the other so less. Thanks for clarification.

Yes, you must use different WP_REDIS_DATABASE values for each domain.

Thanks, i doublechecked that, and i set the password but somehow config did not save my editing of wp cofig where i wrote prefix and database. this is now fixed. Will see if anything is changing. One more question, when i click on Clean Cache in wp admin bar, should that what is 21 MB now, not go to zero? or do i understand that wrong? Value does not change when pressing clear cache. I have there Clean Cache (in german) and Settings and 97,6% 8657/217 21 MB now – if i click clean cache it shows cleaned, but its standig the same 21 MB there. Using php 8.2 if that is interesting

Post your diagnostics please.

Status: Verbunden
Client: PhpRedis (v6.0.1)
Drop-in: Valid
Disabled: No
Ping: 1
Errors: []
PhpRedis: 6.0.1
Relay: Not loaded
Predis: 2.1.2
Credis: Not loaded
PHP Version: 8.2.11
Plugin Version: 2.4.4
Redis Version: 5.0.7
Multisite: No
Metrics: Enabled
Metrics recorded: 322
Filesystem: Working
Global Prefix: "c2h17KNErD_"
Blog Prefix: "c2h17KNErD_"
WP_REDIS_DATABASE: 1
WP_REDIS_PREFIX: "xxxxxxxxxxxxx"
WP_CACHE_KEY_SALT: "xxxxxxxxxxxxxxxxxxxxxxxxxxxx"
WP_REDIS_PLUGIN_PATH: "/var/www/vhosts/XXXX.de/httpdocs/wp-content/plugins/redis-cache"
WP_REDIS_PASSWORD: ????????
Global Groups: [
"blog-details",
"blog-id-cache",
"blog-lookup",
"global-posts",
"networks",
"rss",
"sites",
"site-details",
"site-lookup",
"site-options",
"site-transient",
"users",
"useremail",
"userlogins",
"usermeta",
"user_meta",
"userslugs",
"redis-cache",
"blog_meta",
"network-queries",
"site-queries",
"user-queries",
"code_snippets"
]
Ignored Groups: [
"counts",
"plugins",
"themes",
"theme_json"
]
Unflushable Groups: []
Groups Types: {
"blog-details": "global",
"blog-id-cache": "global",
"blog-lookup": "global",
"global-posts": "global",
"networks": "global",
"rss": "global",
"sites": "global",
"site-details": "global",
"site-lookup": "global",
"site-options": "global",
"site-transient": "global",
"users": "global",
"useremail": "global",
"userlogins": "global",
"usermeta": "global",
"user_meta": "global",
"userslugs": "global",
"redis-cache": "global",
"counts": "ignored",
"plugins": "ignored",
"themes": "ignored",
"blog_meta": "global",
"network-queries": "global",
"site-queries": "global",
"user-queries": "global",
"theme_json": "ignored",
"code_snippets": "global"
}
Drop-ins: [
"advanced-cache.php v by ",
"maintenance.php v by ",
"Redis Object Cache Drop-In v2.4.4 by Till Krüss"
]
Diagnose in die Zwischenablage kopieren

Thanks, so you’re not using the prefix flushing (which is great) that means when you flush the cache and the WordPress admin page loads again it’s loading at least 21 MB just to render the settings page. That’s alright ??

Thanks, what me just wonders, i have 2 sites that mostly use the same plugins, theme and page builder. One shows me on all pages in backend like 20-23 mb there. The other only 2-3 mb even on a page that loads like ages to load all the photogallerys in a tree from database. So just to understand correctly: what it shows in Objekt-Cache in Backend WP Toolbar as Memory is always only from that one page? And not how much of the page is in redis cache in total? Sorry for the maybe dumb questions but i think its a little confusing, or only me. So when i click on clear cache, its normal that it does not clear the cache to zero and fills it one after another again, as it only shows from this single side load in backend.

You could use a tool like Medis, or redis-cli to check out which keys are big and how much space they are taking up.

redis-cli -n <database> -a <password> --bigkeys

Alternatively, drop the WP_CACHE_KEY_SALT because it’s not needed and it takes up additional storage in Redis.