genv 1.4.0

GPU environment and cluster management

Genv - GPU Environment and Cluster Management

Genv is an open-source environment and cluster management system for GPUs.

Genv lets you easily control, configure, monitor and enforce the GPU resources that you are using in a GPU machine or cluster.

It is intendend to ease up the process of GPU allocation for data scientists without code changes 💪🏻

This project was highly inspired by pyenv and other version, package and environment management software like Conda, nvm, rbenv.

🔥 Why Genv?

• Easily share GPUs with your teammates
• Find available GPUs for you to use - on-prem or on cloud via remote access
• Pool the GPUs from multiple machines, allocate the available machine without SSH-ing every one of them
• Switch between GPUs without code changes
• Reserve GPU resources for as long as you use them with no one else hijacking them
• Reproduce your experiment environment easily
• Save time while collaborating

Plus, it's 100% free and gets installed before you can say Jack Robinson.

Documentation

Check out the Genv documentation site.

🏃🏻 Join us in the AI Infrastructure Club!

Looking for a place to discuss best practices, discover new tools, and exchange ideas about how to make the most out of our GPUs without losing time? Join the Discord server with the creators of Genv and rntop - start building your models faster!

• Installation and setup support as well as best practice tips and tricks directly for your use-case
• Discuss possible features
• Monthly Beers with Engineers sessions with amazing guests
• Networking events
• and many more...

🎉 Simple Integration & Usage with your fav IDE

Integration with VSCode (Take me to the installation guide!)

Integration with JupyterLab (Take me to the installation guide!)

A PyCharm integration is also in our roadmap so stay tuned!

License

The Genv software is Copyright 2022 [Run.ai Labs, Ltd.]. The software is licensed by Run.ai under the AGPLv3 license. Please note that Run.ai’s intention in licensing the software are that the obligations of licensee pursuant to the AGPLv3 license should be interpreted broadly. For example, Run.ai’s intention is that the terms “work based on the Program” in Section 0 of the AGPLv3 license, and “Corresponding Source” in Section 1 of the AGPLv3 license, should be interpreted as broadly as possible to the extent permitted under applicable law.