vscode-genv icon indicating copy to clipboard operation
vscode-genv copied to clipboard

GPU Environment Management for Visual Studio Code

GPU Environment Management for Visual Studio Code Join the community at (https://discord.gg/zN3Q9pQAuT) Join the chat at https://gitter.im/run-ai-genv/community

The genv extension lets you interactively control, configure and monitor the GPU resources that your Visual Studio Code session is using.

With genv you could:

  • Easily share GPUs with your teammates.
  • Find available GPUs for you to use.
  • Switch between GPUs without code changes.

Overview

🏃🏻 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 our 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...

Getting Started

Read the genv reference to get started.

Installation

From the Visual Studio Marketplace.

Features

Setting the Device Count

You can configure how many GPUs you need just by clicking the status bar item. After specifying the device count, genv will look for available GPUs and attach them for your environment.

From now on, anything you'll run in your Visual Studio Code session would use only these GPUs (e.g. Python scripts, terminal commands, etc.). You will also see the devices turn green which shows that they are attached to your environment.

Device Count

Choosing Specific GPUs to Use

In addition to automatically provisioning GPUs based on the configured device count, genv lets you choose specific GPUs that you want your environment to use. You can switch between GPUs easily by selecting them in the device view.

Choose GPUs

Development

Setup

npm install

Publish

Bump the version. You can use npm-version. For example:

npm version patch

Package the extension using:

npm run package

Publish the extension using:

npm run publish