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

Integrate TPV #345

Open
jmchilton opened this issue Jun 7, 2017 · 5 comments
Open

Integrate TPV #345

jmchilton opened this issue Jun 7, 2017 · 5 comments

Comments

@jmchilton
Copy link
Collaborator

jmchilton commented Jun 7, 2017

Bjoern is taking over this issue and things we should integrate TPV into the Galaxy deployment.


It would be nice if we had default destination properties (runtime, memory, and cores) for all iuc, devteam, and other commonly used tools - along with a way to scale it for the laptop running docker-galaxy-stable at startup time.

Perhaps even categorizing everything into a runtime (fast, normal, long), a core count (single, few, many), and memory (small, normal, large) would get us a long ways down the road toward good scaling on a laptop and in like a vanilla cloud setting. We could provide additional refinements as they come up.

  • Is this is a good Galaxy hackathon project?
  • Should we provide a table or something we can give to projects and then allow that to be scraped dynamically and aggregated somewhere like ansible-galaxy-extras.
@jmchilton
Copy link
Collaborator Author

Or should we not bother until we have a data-based approach probably involving the GRT?

@bgruening
Copy link
Owner

Ha, see my comment on gitter ;)
@erasche and me talked about a project we would like to start as soon as he is here, which involves GRT, some smart prediction of resources, tools etc.
If someone is faster and would like to work on it even better!

@jmchilton
Copy link
Collaborator Author

GRT is a good project - I told Anton when I started I wanted to do something like that and I have never gotten around to it. I'm wondering if there won't be cases where there is insufficient data or perhaps overfitting by automated approaches - perhaps coming up with some initial categories now and figure out how to map them to various machines would be good and then we could rely on GRT to correct or tweak the categorical assignments... I don't know though.

I was just thinking about this problem because galaxyproject/ansible-galaxy-extras#150 is very cool - but we aren't assigning destinations very well without this data :D. I maybe don't have time to work on this - and should just wait and see what y'all come up with.

@bgruening
Copy link
Owner

We have a master thesis for this, which tries to involve machine learning stuff on this data, maybe even on tools, kind of recommendation system. ping @anatskiy :)

@bgruening bgruening changed the title Default tool allocation settings. Integrate TPV Nov 12, 2024
@bgruening
Copy link
Owner

Change the title and take over the issue. I guess we should deploy TPV by default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants