I've run my Rails app through memory_profiler. There is one Chewy index definition that does not use the "witchcraft" technology. Nevertheless, Chewy comes up at the top of memory allocating gems with 13.6797 MiB, with the witchcraft dependency graph being the most of it:
Yeah, I'm pretty sure it is possible, it just requires some patching which I don't really have time for now. If you will be so kind to send a PR - would be nice.
I've run my Rails app through memory_profiler. There is one Chewy index definition that does not use the "witchcraft" technology. Nevertheless, Chewy comes up at the top of memory allocating gems with 13.6797 MiB, with the witchcraft dependency graph being the most of it:
I believe that should be preventable, since I am not using that part of the code, there should be a way to make it optional, right?