Joost van Doremalen comments

Results 14 comments of


                                            Joost van Doremalen

iOS - Playing local video files uses huge amount of memory

I am seeing the same problem, as @greggarson already said I think it has to do with `Range` requests not being supported.

Large Redis store

@ryansmith94 I don't see any errors in `pm2 logs`. Anything I can check to see whether data can be removed? And if so; how can I safely remove the data?

Large Redis store

Thanks, now deleting those. What about `DEV_STATEMENT_FORWARDING_QUEUE` (I've got a lot of those as well)?

Large Redis store

Mmm strange... it's set to production in the .env file. So all keys prefixed with `DEV_` can be removed as well?

Here's the content of one of the statements: ``` 127.0.0.1:6379> HGETALL bull:DEV_STATEMENT_FORWARDING_QUEUE:4213125 1) "opts" 2) "{\"removeOnFail\":false,\"removeOnComplete\":false,\"attempts\":1,\"delay\":0,\"timestamp\":1546567921384}" 3) "priority" 4) "0" 5) "data" 6) "{\"statementId\":\"5c2ec0eddcbf3d6969956ab6\"}" 7) "name" 8) "__default__" 9) "delay"...

Large Redis store

Here's the output: ``` Sampled 8297439 keys in the keyspace! Total key length in bytes is 337395319 (avg len 40.66) Biggest string found 'bull:DEV_STATEMENT_QUEUE:stalled-check' has 13 bytes Biggest list found...

Large Redis store

I've removed the `DEV_` keys, but it seems some have returned: ``` redis-cli --scan --pattern bull:DEV_* bull:DEV_STATEMENT_PERSON_QUEUE:stalled-check bull:DEV_STATEMENT_FORWARDING_QUEUE:stalled-check bull:DEV_STATEMENT_FORWARDING_DEADLETTER_QUEUE:stalled-check bull:DEV_PERSONA_IMPORT_QUEUE:stalled-check bull:DEV_STATEMENT_QUERYBUILDERCACHE_QUEUE:stalled-check bull:DEV_STATEMENT_FORWARDING_REQUEST_DELAYED_QUEUE:stalled-check bull:DEV_STATEMENT_FORWARDING_REQEUST_QUEUE:stalled-check ``` Is this problematic?