Skip to content
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

Adding sorting to solver matching algorithm #492

Open
bgins opened this issue Jan 16, 2025 · 0 comments · May be fixed by #497
Open

Adding sorting to solver matching algorithm #492

bgins opened this issue Jan 16, 2025 · 0 comments · May be fixed by #497
Assignees
Labels

Comments

@bgins
Copy link
Contributor

bgins commented Jan 16, 2025

General Description

The solver matches job offers and resource offers by a machine spec and statistics constraints. In addition, the matching algorithm may sort job offers and resource offers before, during, or after constraints matching.

We will add the following sorts to the initial version of the matching algorithm:

  • Job offers are sorted oldest first
  • When considering a job offer in fixed pricing mode, sort resource offers by oldest offer first
  • When considering a job offer in market pricing mode, sort resource offers by cheapest offer first
    • If multiple resource offers offer the same cheap price, sort the resource offers again oldest first

Which system(s) or functionality does this affect

The solver is affected directly. The matching algorithm has indirect consequences on resource providers and job creators.

Describe the changes, and how this affects/ interacts with each system.

The implementation will be entirely in the solver. We will add sorts once defined where appropriate in the matching code.

@bgins bgins added the solver label Jan 16, 2025
@bgins bgins self-assigned this Jan 16, 2025
@bgins bgins linked a pull request Jan 29, 2025 that will close this issue
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant