Compute Limits are now easier to use

We improved Compute Limit management for team administrators.  Compute Limits assist teams in monitoring and restricting monthly compute spend by providing fine-grained control over compute usage.  You can now create and edit email alerts and absolute maxes for both teams and team members from the billing page.  Administrators will receive an email when an alert or max amount is reached, and users will be notified in-app if they are blocked from accruing additional compute.  We hope these changes will give administrators more insight and control over their monthly spend.

For more information about Compute Limits, please visit our documentation.

Fixes & Improvements

  • Added the ability to edit team names
  • Improved invoice clarity by adding a section to represent Gradient storage costs
  • Improved visibility into Core machine status by more accurately rendering real-time machine state
  • Fixed a bug where some users could not scroll on streaming Core machines
  • Fixed a bug where non-US countries were not selectable during signup onboarding

Fixes and Improvements

Over the past few weeks, we've shipped a number of improvements to improve your product experience.

  • Improved private network performance and stability in AMS1: A major upgrade has been completed for the network infrastructure in AM1 resulting in increased performance and stability of the network.
  • Improved reliability of machine starts: Starting machines will now encounter fewer issues due to improved automatic remediation of event errors.
  • Improved availability of GPUs: Resolved an issue where specific machine types GPU availability were lower than expected.
  • Prevent users from accidentally creating machines from deleted custom templates: There was an issue that allowed users to create machines from deleted templates resulting in inaccessible machines. Users will now see an error message if they try to create a machine from a deleted template.
  • Improved management of inaccessible machines: Users can now shut down and deactivate machines that are inaccessible from the list views and details view.
  • All new Linux machines have a dynamic public IP by default: A public IP is currently required to access a Linux machine except on a private network. By default, a newly created machine will have a dynamic public IP assigned.
  • Improved summary of billing charges on machine create: We have improved the machine create billing summary to better reflect the total cost for creating and running a machine. Prices are broken down into monthly and active charges to differentiate the costs of running machines vs having machines active.
  • Improved network performance and reliability: We’ve made a change to our QOS policy that now results in greater network availability and reliability for all machines.

Gradient Models are easier to upload

We’ve enhanced the Gradient model upload process through the console and CLI. You can now track progress of the model upload, bring in nested directories and more gracefully handle upload errors and aborts.

Previously, the model upload dialogue would not show you progress and allowed you to close it before the model would complete. This could cause upload failures mid-process. This now lets you know exactly what is being uploaded!

We have also parallelized large uploads by splitting them into chunks, making better use of bandwidth and drastically reducing the amount of time it takes for an upload to finish.

Lastly, the CLI prevents users from uploading with an old version of the CLI which was previously breaking the ability to get data into Gradient.

Fixes & Improvements

  • Fixed a bug causing the workflows status pagination to limit itself to 2 pages
  • Fixed a bug that did not allow you to rename files in the Gradient Notebook file manager
  • Fixed a bug causing readiness errors in notebooks
  • Updated the Gradient Notebooks Rapids runtime to RAPIDS 20.08
  • Fixed a bug that caused the edit button in Gradient Deployment Specs to be stuck in a perpetual load
  • Added the ability to update certain Notebooks to the newest version of our Gradient container
  • Fixed a bug that allowed users to choose an IPU on the Fast.ai runtime
  • Added two shortcuts to Gradient Notebooks: Markdown (m) and code(y)
  • Improvements to the project page to more easily create notebooks and deployments

Autosave, revamped logs, file manager improvements, and more! 💾

We've added a number of new features to Gradient Notebooks, including autosave, improved access to logs, and a host of file management features.

Let's dive in!

Enable autosave in Gradient Notebooks! improvement 

Autosave is now available in Gradient Notebooks. Enable autosave with the button in the bottom right of the IDE.

When autosave is enabled, your notebook will save automatically every thirty seconds.

New panel in the IDE for logs improvement 

Logs have received a refreshed look and feel! We've moved the logs pane from the sidebar to the main window in the IDE. We think this provides a much more comfortable amount of real estate to scroll through system logs. 

Toggle the log pane using the button in the bottom left corner of the IDE above the IDE host metrics.

New file manager CRUD capabilities are now available offline! improvement 

We've added a number of new CRUD capabilities to the IDE -- and not just that but these capabilities are available when your machine is offline! 

The list of upgrades includes uploading and deleting multiple files and/or folders as well as drag-and-drop capabilities for moving multiple files and/or folders.

In addition, we've added the ability to duplicate files and/or folders.

Bugfixes fix 

  • We fixed a bug that sometimes caused the terminal window pane to resize incorrectly
  • We fixed a bug that prevented access to secrets from within a notebook
  • We fixed an issue with font rendering in the terminal


Autosave, private notebooks, a number of bugfixes, and more! 🧑‍🔧

We've released a number of improvements and bugfixes for Gradient!

Gradient Notebooks now autosave by default improvement

We've improved the autosave functionality of notebooks! Whereas before only .ipynb files would save automatically, we now provide autosave functionality for all filetypes within notebooks.

Notebooks running on free GPU instances can now be private on Pro or Growth subscriptions improvement 

If you're on the Gradient Pro or Growth plan, notebooks that run on Free GPU instances can now be made private.

PyTorch container updated to version 1.10, TensorFlow container updated to 2.6.0 

We've updated both PyTorch and TensorFlow default containers in Gradient Notebooks to their latest stable release versions. The new runtimes are now available in the Gradient console. 

Other improvements

  • Gradient Deployments are now able to pull from models registered in Gradient
  • Overall GPU capacity has increased after addressing an issue related to read-only filesystems used by Gradient Notebooks

Bugfixes

  • We fixed a bug in the notebook create menu that sometimes caused the Workspace URL field not to update when selecting a new runtime
  • We fixed a bug in notebooks that sometimes caused deleted files to linger in the file management pane
  • We fixed a bug in notebooks that caused an empty file to be added to new directories
  • We fixed a bug that sometimes generated duplicate and triplicate notifications when switching teams


What’s New 🚀 in 7.2.5

UX & Performance

The performance of various has been optimized to load faster & the design of a couple modals couple (upgrades, accounts) have been improved.

Billing

There is now an option to receive an email after billing runs each month. Find this under Team->Billing->Recent Invoices.

Core

The native app now supports QUIC by default - the latency experienced
during streaming a virtual desktop is minimized without incurring any
hits to performance

Gradient

Added social profiles, the ability to make notebooks public/shareable to your friends & a free GPU. These features are in closed beta at the moment, reach out to support to have it enabled.

Continue to make improvements to the CLI (https://github.com/Paperspace/gradient-cli/releases)

Bug fixes to model processing where the summary for tensorflow models was not getting populated correctly.