Haris Aqeel

> hi folks, the only recent changes that involves new keys are the new repeatable structure: when you create new repeatable jobs a new key for a repeatable job is...

> > hi folks, the only recent changes that involves new keys are the new repeatable structure: when you create new repeatable jobs a new key for a repeatable job...

> hey @Haris-SP4RKy could you also inspect you redis keys, if there are any key containing `:repeat:` or `:de:`? bull:TASK_NOTIFICATION_QUEUE:repeat:34bbc9e9064ac54259859101ce9f0b23:1725382800000 This is one of the example key it has repeat

> @Haris-SP4RKy just to clean up a bit the context here. Are you experiencing this large memory consumption after an upgrade of BullMQ or is it unrelated to the BullMQ...

> @Haris-SP4RKy you can also use this command to inspect the memory consumption of a given key: https://redis.io/docs/latest/commands/memory-usage/ This could help you find which key or keys is consuming more...

@manast I have only keys that have repeat in it, no others keys other than that. there are no keys that have id as postfix

`bull:DAILY_NOTIFICATION_QUEUE:repeat:616f4e64f45c20b7485be92e8a06a9c3` `bull:DAILY_NOTIFICATION_QUEUE:repeat:d4000a6b6778333f9c251f35877a9d9c:1725408000000` `bull:CLASS_NOTIFICATION_QUEUE:USERS:NOTIFICATION:CLASS:00402233-d2ca-47a6-8d73-3717f73b1a78:82ccf8ea-72b3-478f-a372-f06d5f2deca7` All keys are of these structures. Last one is for delayed job, others two from repeatable