Alexander Schepanovski

> So IMO returning a None ODB (and not using "default DVC remote ODB") during object collection is the correct behavior. It might be understood like that. But after collection...

From the top of my head: ```python from funcy import join_with, all, is_mapping def deepmerge(*dicts): return join_with(deepmerge, dicts) if all(is_mapping, dicts) else dicts[-1] ```

`CACHEOPS_REDIS` is passed as is to `redis.StrictRedis` or to the `redis.StrictRedis..from_url()` so it should be filled in is redis-py docs.

Not sure why would I stop you

I think tests and benchmarks should be separated. Can't think of a situation when I want to run both tests and benchmarks in a single call. This is being the...

If the current thing were in the same spot each time I will need to just look at first line and see if it's green, now I need to be...

That would solve this

Mostly, the other thing is I need to group by name now, but would prefer to sort by it. Too many empty or techy lines in report when grouping.

Now [it's two](https://github.com/Suor/django-pickling/blob/master/tests/bench.py). Maybe I don't get how this should work, but what's the point in comparing run time of completely different actions? 

But why anyone needs to compare different stuff? Isn't a usual use case is to compare same stuff that changes over time?