Richard Schneeman
Richard Schneeman
Not sure why that would happen here though. I don't think that we load assets concurrently. The error is coming from ``` ruby asset = cache.get(key, true) if asset asset[:metadata][:dependencies].map!...
> I am sorry but I can not share the code of the project I am working on. Sorry didn't specify, I really don't want your code. I want a...
Tried to repro the behavior with a ruby only script and i'm not able to ``` ruby require 'set' require 'securerandom' while true hash = {} hash[:nested] = {} hash[:nested][:set]...
@jeremy right now assets are loaded one at a time since they have dependencies that needed to be loaded in order. Theoretically we could parallelize it but it would need...
Not sure the best way to move forwards here. If the issue exists only in development we don't want to slow down prod to fix dev. I'm still not 100%...
I won't be able to dig in until after RailsConf
This is different than the concurrent-ruby example linked.
We know exactly what is happening, it's just that to solve it would cause performance problems in production which we don't want. Maybe try using some other cache backends and...
I agree that PR would solve the problem, however in production we want to mutate the original arrays as there is a performance penalty for allocating additional objects. Maybe if...
Can you put it somewhere I can reproduce your benchmarks?