admin.hub.nuxt.com has a timeout occurred when cache is large

[oritwoen]

Describe the bug
In the hub panel, you can't access the cache and a timeout occurs. This only happens with large databases for CACHE. When I clear the entire KV from the cache or have little of it, everything works correctly.

[atinux]

180k records, I see, very interesting amount, will have a look to improve!

[oritwoen]

Yes, I connected Nuxt Hub to a client's website that is several years old, has tens of thousands of entries and relations. For now, it is based on WordPress's wp-json with a cache for each tag, category and entry.

The traffic there is at the level of 40-100k visits per day. And NuxtHub works great, but the only such a nuisance is that timeouts are in the panel for the cache.

Although recently I am leaning towards connecting db0 from unjs and connecting to the database directly to connect to mysql directly, bypassing wp-json and not doing so much caching because with such traffic it gets very expensive.

It would be the best if hyperdrive supported mysql (I'm waiting xD) and then everything would be simpler.

I wrote a bit, but this is the context. If you want more information, logs or statistics from such high traffic, let me know, I will send it.

[luminous8]

I'm having the same issue while having way lower values (except storage)

[atinux]

I will have a look at it very soon, sorry for the delay

[luminous8]

Hey @atinux

Have you had a chance to look at it?

[atinux]

Still on my roadmap, sorry for the delay

[luminous8]

I really need to clear the clear the cache to fix some SEO issues

I have lots of KV entries

i thought of deleting the KV store in cloudflare directly but i cannot find a way to bind a KV store in NuxtHub

any workaround idea that could do the job easily here?

[atinux]

Quick and dirty way would be to go to your Cloudflare project:

1. unbind the KV namespace
2. Go to your KV namespace and delete it
3. Create again the namespace with the same name
4. Go back to your CF project and bind it again
5. Retry latest deployment