pelias / pelias/parser

performance testcases

Open
#62 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
64
Forks
26
PR merge metrics
No merged PRs in 30d

Description

This issue is to track some queries which cause the library to take a long time (>50ms)

  • 310 4848 Virginia Beach blvd Virginia Beach, va 23562, Virginia Beach, VA, USA
  • airport road n and golden gate pkwy off ramp e, naples, fl

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the two listed address queries through the parser and measuring their execution time. Identify how performance is currently tested, then define reproducible test cases for queries exceeding 50ms. Done means the slow cases are captured in tests and their expected performance behavior is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.