Lucas_Werkmeister_WMDE added a comment.
> My understanding of the documentation for mw.wikibase.getBestStatements is that it only loads the one property that's queried, not the whole object, so there would be no reason why querying a large object would differ in performance from querying a small object. No, it has to load and deserialize the whole entity (though it only returns a small part of it), since it’s all stored as one JSON blob. (I believe the result is then cached on several levels, so subsequent requests for other properties from the same entity have a chance of being more efficient.) We might be able to improve on this eventually, but I don’t think there’s any surprising hidden costs at play here which we could easily fix. TASK DETAIL https://phabricator.wikimedia.org/T237884 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Lucas_Werkmeister_WMDE Cc: Lucas_Werkmeister_WMDE, Aklapper, Reinhard_Mueller, Liuxinyu970226, darthmon_wmde, DannyS712, Nandana, Lahi, Gq86, Darkminds3113, GoranSMilovanovic, QZanden, LawExplorer, Vali.matei, _jensen, rosalieper, Scott_WUaS, Jonas, Volker_E, Wikidata-bugs, aude, GWicke, Dinoguy1000, Lydia_Pintscher, Mbch331, Jay8g
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
