>> This is part of a bigger issue we should work at doing better at for >> Solr 6: debugability / supportability. >> For a specific request, what took up the memory, what cache misses or >> cache instantiations were there, how much request-specific memory was >> allocated, how much shared memory was needed to satisfy the request, >> etc.
Oh, and if we have the ability to *tell* when a request is going to allocate a big chunk of memory, then we should also be able to either prevent it from happening or terminate the request shortly after. So one could say, only allow this request to: - cause 500MB more of shared memory to be allocated (like field cache) - only allow it to use 5GB of shared memory total (so successive queries don't keep upping the total amount allocated) - only allow 100MB of request-specific memory to be allocated -Yonik
