aude added a comment. only one data point comparison on my dev wiki and obviously can't reproduce all production conditions, but:
recent changes with EntityTermLookup (30 days, 60 items) - TermSqlIndex: 65955512 memory 28786 backend response time recent changes with EntityRetrievingTermLookup (30 days, 60 items), few cache misses: 70434344 memory 20670 backend response time recent changes with EntityRetrievingTermLookup (30 days, 60 items), have restarted memcached so many cache misses: 70634728 memory 33539 backend response time neither is really a good choice. using TermSqlIndex queries are somewhat better in regards to memory usage, while EntityRetrivingTermLookup seems better if cache misses are few enough. these results are also consistent with comparisons i had made on the EntityView (before we had EntityIntoTermLookup). if we can somehow profile in production (with reasonable effort), would be good and interesting. and overall, continue to work on batched lookup and caching in as many places as possible. TASK DETAIL https://phabricator.wikimedia.org/T74309 REPLY HANDLER ACTIONS Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign <username>. To: aude Cc: Tobi_WMDE_SW, Liuxinyu970226, Wikidata-bugs, daniel, aude _______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
