Performance improvement/Testing around un-used properties

[jmbrunskill]

Right now we often query a lot more data that needed from dgraph for the user's query. For example getting all properties when we aren't using any.

Investigate if this has a significant performance impact, and see if there's a nice way to reduce this overhead

1. Use loaders for properties, children,parents, and other related entities
2. Have a dedicate type and endpoint for a faster smaller response type when extra data isn't needed?

we do this entities query for all items for the fuzzy search - especially as we add more items I can imagine this query getting slow?

Yeah, it definitely doesn't feel great. Could compare speed to using a loader for all properties? Still seems fast locally on good hardware, but I agree!

Originally posted by @jmbrunskill in #606 (comment)