Hello guys, have a quick question.
I’m sort of confused about a claim publish-lookups makes however.
publish-compositedoes not scale well, because in the second level queries it will create
Ncursor observers, where N is the number of documents returned in Primary query. This behavour will overload your database.
I found this interesting as I use publish-composite at the moment.
I tested the statement out by publishing a total of 26 documents with publish-composite (1 parent, 25 documents). Galaxy’s APM shows that I only created 2 observers - the same as what publish-lookups would have created.
Is publish-lookups comparing itself with an outdated version of publish-composite? Does publish-composite really create 2 observers in a case like the above?