"pieces search "print"" taking a long time to resolve on a large snippet database

[mark-at-pieces]

for first touch it looked like search was not resolving but then I realized it took a very long time, wonder if we should take a look into performance here:

specifically will want to show the results as soon as possible then fetch on the fly.

**ALSO Note: will want to verify that we are running the search w/ transferables=FALSE

[hal-8999-alpha]

Hmm. The default search is fuzzy so I assume that may be linear and that you have a lot of assets.

And yes, transferables=FALSE throughout the entire app.

[mark-at-pieces]

I can send over the response times, they are sub second responses, so has to do with the fetching on the plugin side

[mark-at-pieces]

so basically to ensure this is as fast as possible you return the minimum information to the client, and then only fetch the additional data if and only if they are digging deeper into the asset