Question regarding LQE.
When we update a service provider to include or exclude a container, this triggers updating the Selections of all Configurations in the service provider.
The serialized RDF of a Selections with 1 million elements takes about 250MB to transfer to LQE. LQE is also capable of querying several resources in parallel so it is possible to have several Selections queried at the same time.
Obviously all of this takes a lot of memory and a lot of network traffic.
Has anybody here already dealt with big Selections resources when working with TRS / LQE?
Are there some recommendations on how to deal with such large Selections resources? Paging maybe?