Skip to content

Use the serializer context to get an element's corpus

Erwan Rouchet requested to merge corpus-context into master

Requires !1305 (merged), Closes #700 (closed)

This removes some remnants of the old ListElements in which filtering by corpus was only optional, and uses the fact that all elements in ListElement{s,Children,Parents} are now of the same corpus to use the serializer context to send the corpus instead of retrieving the same corpus dozens of times in an SQL JOIN.

This removes an entire Hash Join on all the retrieved elements before the LIMIT is applied, shaving off 15% of the endpoint execution time on GoLFor (a corpus with 4 million elements on my local DB).

Edited by Erwan Rouchet

Merge request reports