Kainoa Kanter

I cleared the queue. Reverting back to e3086f56a106ef4d7d2da4cc3748127a93def69e works fine, but updating again to cde6adb34d1dd016a03cdb875bf14ba2311d9244 produces a few of generic queue errors (i.e. `[queue inbox] error Error processing job`), but...

No, I use the build from source method to make a release build from the latest git commit, and I already have that commit in the build.

I wonder if I should migrate from bull to bullmq for additional testing, I'm not sure how many people use bull compared to bullmq :thinking:

I'm noticing some interesting graph patterns. Normally, Redis would have jobs constantly in delayed/processing and have a steady stream of active jobs, and not have repeating patterns like this. 

Over the last couple of days, here are the biggest things I've noticed when comparing how Redis operates with Bull vs Dragonfly with the exact same limits/configs: - With Dragonfly,...

Exactly, and I'm aware. Just happy to share my observations to help see what behaviors occur and if they end up being fixed with updates :)

I'm currently adapting this PR, and using [ics](https://www.npmjs.com/package/ics) for iCal generation

Ah, gotcha. I'll close this as invalid then.

I got the info by looking at `top` and dividing the percentage by the amount of total ram. Here's `INFO`: ``` 127.0.0.1:6379> INFO # Server redis_version:6.2.11 dfly_version:df-dev redis_mode:standalone arch_bits:64 multiplexing_api:iouring...

``` # Memory used_memory:6886880 used_memory_human:6.57MiB used_memory_peak:7471824 comitted_memory:304283648 used_memory_rss:250556416 used_memory_rss_human:238.95MiB ``` Interesting... what's the difference between `used_memory_human` and `used_memory_rss`?