# Suggested Topics - Title & Content based Suggestions

**URL:** <https://meta.discourse.org/t/suggested-topics-title-content-based-suggestions/173354>\
**Category:** Feature\
**Tags:** suggested-topics\
**Created:** [December 15, 2020, 7:52am UTC](https://meta.discourse.org/t/suggested-topics-title-content-based-suggestions/173354 "2020-12-15T07:52:29Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![nhpackard](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nhpackard/32/224328_2.png) [@nhpackard](https://meta.discourse.org/u/nhpackard)\
**Post date:** [July 3, 2021, 1:45pm UTC](https://meta.discourse.org/t/suggested-topics-title-content-based-suggestions/173354/12 "2021-07-03T13:45:35Z")

</div>

Thanks for the pointer to the table implementation. Not sure the table approach scales, though. For N topics, we need a table of size N^2. so for 10^4 topics the table would have 10^8 entries.

I don’t see how to escape needing a python call to parse a new topic, embed it, and find the nearest neighbors. I have in the past built a web interface, but I would probably be tempted here to just run a python process on the side and communicate with discourse through a socket or pipe, looking more or less like read and write to a file rather than an actual python call. (It’s all running on my server, after all…)

---

_[View the full topic](https://meta.discourse.org/t/suggested-topics-title-content-based-suggestions/173354)._