Queue Length about clip

[kazjote]

All events are stored as separate values in Redis (am I right?). It is quite possible that you are just out of space.

You could try decreasing :event_data_ttl parameter as shown here: https://github.com/paulasmuth/fnordmetric/blob/master/doc/full_example.rb#L635 . By default it is set to 1 month. But it will only take effect for newly added events.

[chrismoos]

The TTL isn't a bad idea but I run out of memory within hours, so I don't think its going to help.

[kazjote]

You can experiment and set it to 5 minutes :) Do you use uniq gauges and sessions?

[JohnMurray]

Have you tried running multiple instances? If you run multiple instances on the same machine (even with the same configuration), it will notice a web-server interface running and just start up another worker process.

I'm working on a commit now that will allow Fnordmetric to spawn off multiple workers via multiple processes.

[catz]

you should definitely run more workers and decrease event_data_ttl parameter. I run several workers via self.embedded (thin) monitored by god. My queue is always 0 now. It's about 2000 events for 3 seconds flow now.

imo 8 millions unprocessed events - totally unreal case

[chrismoos]

Yeah seems like more workers and TTL is the way to go, going to try this out. Thanks everyone.