Added blog post semantic search in postgres in 15 minutes #1535
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
montanalow
reviewed
Jun 18, 2024
|
|
||
| We used the [pgml.embed](/docs/api/sql-extension/pgml.embed) PostresML function to generate an embedding of the sentence "Generating embeddings in Postgres is fun!" using the [mixedbread-ai/mxbai-embed-large-v1](https://huggingface.co/mixedbread-ai/mxbai-embed-large-v1) model from mixedbread.ai. | ||
|
|
||
| The output size of the vector varies per model, and in _mxbai-embed-large-v1_ outputs vectors with 1024 dimensions: each vector contains 1024 floating point numbers. |
There was a problem hiding this comment.
Suggested change
| The output size of the vector varies per model, and in _mxbai-embed-large-v1_ outputs vectors with 1024 dimensions: each vector contains 1024 floating point numbers. | |
| The output size of the vector varies per model, and in `mxbai-embed-large-v1` outputs vectors with 1024 dimensions: each vector contains 1024 floating point numbers. |
I think we should use backticks for all identifiers, rather than italics.
There was a problem hiding this comment.
They don't render very nicely in our docs imo:
A few options here:
- Increase line height, may help with the rendering.
- Remove the border from the code blocks, making them less jarring.
- Not use inline code blocks at all, since they don't really add to the readability at the moment.
There was a problem hiding this comment.
I agree that we could make some design improvements here. It'd be good to bring this up with the design team. We should still consistently use semantic markup, so that when the style is fixed, we get the benefits.
|
|
||
| !!! | ||
|
|
||
| Now trying our search engine again: |
There was a problem hiding this comment.
This would be better illustrated with a graph at 10, 100, 1000, 10000, 100k, 1M. Show that Big O.
Co-authored-by: Montana Low <montanalow@users.noreply.github.com>
Co-authored-by: Montana Low <montanalow@users.noreply.github.com>
Co-authored-by: Montana Low <montanalow@users.noreply.github.com>
Co-authored-by: Montana Low <montanalow@users.noreply.github.com>
Co-authored-by: Montana Low <montanalow@users.noreply.github.com>
Co-authored-by: Montana Low <montanalow@users.noreply.github.com>
Co-authored-by: Montana Low <montanalow@users.noreply.github.com>
levkk
reviewed
Jun 18, 2024
|
|
||
| If you have any questions, or just have an idea on how to make PostgresML better, we'd love to hear from you in our [Discord](https://discord.com/invite/DmyJP3qJ7U). We’re open source, and welcome contributions from the community, especially when it comes to the rapidly evolving ML/AI landscape. | ||
|
|
||
| ## Closing thoughts / why PostgresQL? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.