Evaluate(@DbLookup...) v GetDocumentByKey

Just started looking at changes to an existing app which retreives the fields from the configuration document with a whole series of Evalaute(@DbLookup…) in the script agents? Surely this must be significantly slower than using GetDocumentByKey and then setting the fields. In one agent it sets 12 different fields with 12 @DBlookups in the Evaluate statement. Any rhyme or reason why it may have been coded this way?

Subject: Evaluate(@DbLookup…) v GetDocumentByKey

read part

Sometimes the advantage is performance

maybe it is answer to your question. in any case will leave here a post when you finish to discover -why-