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
While debugging some performance issues I looked at the watchStuckJobs implementation and saw kue uses the KEYS redis command. Redis recommends that this command should be avoided in production environment due to its complexity (O(n) on the number of keys). https://redis.io/commands/keys
Could you fix this? Or at least stop strongly suggesting using this command? The performance impact is significant with a big enough database.
Regards
The text was updated successfully, but these errors were encountered:
The use of KEYS in a production environment is one of the biggest no-nos in Redis. I'm happy to hear this is no longer needed, but it has to be deprecated asap. Users are actually calling this "workaround" and are experiencing performance issues with their servers.
Hello,
While debugging some performance issues I looked at the watchStuckJobs implementation and saw kue uses the KEYS redis command. Redis recommends that this command should be avoided in production environment due to its complexity (O(n) on the number of keys). https://redis.io/commands/keys
Could you fix this? Or at least stop strongly suggesting using this command? The performance impact is significant with a big enough database.
Regards
The text was updated successfully, but these errors were encountered: