llnl / llnl/merlin

Get Status Commands to Use Database

Open
#534 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement Merlin 2.0 refactor
Dominant language
Python
Stars
151
Forks
30
PR merge metrics
No merged PRs in 30d

Description

The merlin status and merlin detailed-status commands simply do not do well at scale since we're handling thousands of status files. We need to change this functionality so that the status commands utilize Merlin's new database instead which should drastically improve query performance.

To accomplish this we need to:

  • Add new data models and database commands
  • Link new data models to existing functionality
  • Refactor status classes

This issue will not be marked complete until all subtasks are finished.

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 with the merlin status and merlin detailed-status command entry points, then inspect the existing status classes and Merlin's new database functionality. The work is complete when the data models and database commands are added, linked to existing functionality, and both status commands use the database for improved performance; all subtasks must be finished.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli, database
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.