Skip to content

Fix: Change suggested batch size to 5 to help with cpu limit issues #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 23, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
@@ -917,7 +917,7 @@ Now let's add logic to generate embeddings automatically anytime new rows are ad
after insert on document_sections
referencing new table as inserted
for each statement
execute procedure private.embed(content, embedding, 10);
execute procedure private.embed(content, embedding, 5); -- changed this to 5 to help with reports of CPU limits reached
```

Note we pass 3 arguments to `embed()`:
2 changes: 1 addition & 1 deletion supabase/migrations/20231007002735_embed.sql
Original file line number Diff line number Diff line change
@@ -54,4 +54,4 @@ create trigger embed_document_sections
after insert on document_sections
referencing new table as inserted
for each statement
execute procedure private.embed(content, embedding, 10);
execute procedure private.embed(content, embedding, 5);