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.

Sign up for GitHub

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

Jump to bottom

Make gitbase suitable to run over PGA #16

Closed
4 tasks done
smola opened this issue Mar 27, 2018 · 5 comments
Closed
4 tasks done

Make gitbase suitable to run over PGA #16

smola opened this issue Mar 27, 2018 · 5 comments
Labels
P0 high priority T:Data Retrieval Data Retrieval objectives T:Engineering Engineering objectives

Comments

@smola
Copy link
Contributor

smola commented Mar 27, 2018 •
edited
Loading

Parent objective: #8
Progress: 4/4

  • [P0] Make gitbase better suited for rooted repositories
  • [P0] Make gitbase queries on PGA not crash
  • [P1] Instrument gitbase to be able to trace performance
  • [P1] Improve performance of gitbase over PGA
@smola smola added the P0 high priority label Mar 27, 2018
@marnovo marnovo mentioned this issue Mar 27, 2018
Closed
4 tasks
@smola smola added the T:Engineering Engineering objectives label Mar 27, 2018
@ajnavarro ajnavarro mentioned this issue Mar 27, 2018
Closed
3 tasks
@smola smola added the T:Data Retrieval Data Retrieval objectives label Apr 2, 2018
@ajnavarro
Copy link

ajnavarro commented Jul 2, 2018 •
edited
Loading

  • [P0] Make gitbase better suited for rooted repositories
    We can close this one because now is better suited for rooted repos than 4 months ago.

  • [P0] Make gitbase queries on PGA not crash
    Queries over PGA will not crash. We added a flag to gitbase to be able to continue if we encounter some git error.

@smola
Copy link
Contributor Author

smola commented Jul 2, 2018 •
edited
Loading

I assume that basic instrumentation is already there, and that performance improved a lot with indexes. Although the objective itself "gitbase suitable to run over PGA" is probably not fully achieved?

@ajnavarro ajnavarro reopened this Jul 2, 2018
@ajnavarro
Copy link

The main objective is not done yet. Should we re-define it again with other more accurate bullet points or keep that here and add new points to the actual ones?

@smola
Copy link
Contributor Author

smola commented Jul 2, 2018

@ajnavarro We have defined another gitbase performance improvement objective for Q3.
@eiso What do you think?

@ajnavarro
Copy link

Closing it as done. Opening new gitbase performance improvements OKRs for Q3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
P0 high priority T:Data Retrieval Data Retrieval objectives T:Engineering Engineering objectives
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@smola @ajnavarro