Optimize Label Filtering

[jue-henry]

Currently, we are still seeing query timeouts on mongodb , and the requests seem to be exclusively involve some form of label filtering. I am proposing 2 options:

1. optimize existing label filtering, currently the label filtering via the mongodb query seems very unintuitive. I think research can be done to potentially root out why it was initially done this way and improve on it
2. move label filtering server side. This is the next most intuitive option to attempt to address this issue, as filtering can be fairly easily done through code. We query the db with the other options provided and after we filter via the labels. The main worry with this option is to not break pagination if we must rerequest images if the minimum is not reached due to the server side label filtering

[nathanielrindlaub]

@jue-henry thanks for continuing to push on this! What do you mean by "label validation" exactly? Are you talking about image queries that include some kind of validation state check, or are you talking about actual label validation mutations (e.g. when a user validates a label)?

My recommendation would be start with option 1. I think a fresh set of eyes would be super welcome here, and if we can make any of the label validation more efficient I'm all for it.

Number 2 is interesting, but I'd also add the concern that that could consume a huge amount of memory if we're needing to load potentially millions of image records in memory and then filter them.

[nathanielrindlaub]

Related: #119

[jue-henry]

@nathanielrindlaub Sorry will clarify in the issue itself as well, but I mean label filtering/searching via the labels