Hello, I'm experimenting with a tool that matches ...
# community-help
j
Hello, I'm experimenting with a tool that matches candidates to job listings (roughly ~200k listings usually), I'm seeing a very strong degradation in performance as the
query
field grows in size, the below query returns 11 results out of 200k, where using
exhaustiveSearch
returns many more, but often crashes or times out. Is there any best practices I can look at to improve the performance of a query like this? Maybe using vector search instead?
Copy code
{
  "indexName": "listings",
  "query": "Software Engineer III Technologies: React.js, Next.js, TypeScript, Redux, Python, Node.js, GraphQL, JavaScript React.js Next.js TypeScript Jest Playwright Cypress Redux Python Node.js GraphQL PNPM SQL JavaScript CSS HTML",
  "queryBy": "jobTitle,jobSummary,requiredSkills",
  "queryByWeights": "3,2,1",
  "sortBy": "_text_match:desc",
  "includeFields": [
    "jobTitle",
    "jobSummary",
    "requiredSkills",
    "createdAt"
  ],
  "prefix": "false,false,true",
  "perPage": 10,
  "page": 1
}
whoa, paginating through these returns extra results. my bad. this might be ok!
switched queryBy to
embedding
with great results