Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upSupport GPU resource request #159
Open
Labels
Comments
|
Thanks for this issue. Support for multiple resource utilisations is definitely on our radar. We are open to any PRs related to this. @mcrute May be working on GPU support PR if I recall correctly? |
|
I have a working patch for GPU support and will get it cleaned up for PR early next week. It doesn't yet go so far as to generalize the resource utilization model but I hope to build in that direction in the near future. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, Escalator calculates resource utilisations based on both CPU and RAM. IMO, it's better to let users have multiple choices between: