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


Introducing a new docs experience for Core and Gradient! πŸ“š

New docs come to Paperspace! announcement 

We're excited to introduce an entirely new unified docs experience for Paperspace! 

After maintaining several different systems for documenting different parts of the product, we're eager to announce that Paperspace docs are now available in a single location with a new unified theme and organizational structure!

You can now find Core documentation, Gradient documentation, and general Account Management documentation all in one place!

If you need a place to start, we recommend starting with the Core overview or the Gradient overview -- you'll be able to launch right into tutorials, guides, and reference materials designed to help you succeed with Paperspace.

Have an idea for how to improve Paperspace documentation further? Please send us a note with any comments or suggestions!

All-new Linux SSH experience and improved machine create experience in Core! πŸ›«

We're excited to announce some brand new Core experiences! Let's jump right into what's new.

All-new Linux SSH experience announcement 

We've reconfigured the Linux machine create experience to optimize for connecting to Linux machines via SSH.

We feel that a direct connection to a Linux machine is a fantastic experience. We'll still support Linux VMs in the browser, but if you get a chance, give SSH a try -- it's so easy to connect!


Managing machines just got a lot better announcement 

We've also released a substantial cleanup of the machines settings page in Core which has made it easier than ever to access and manage machine settings. 

Let's say for example we wanted to create a snapshot of our new machine -- easy!

Or let's say we wanted to update our machine name and adjust the autoshutdown timer? Also easy!

We've also made it easier to do things like assign public IPs, generate templates, and more!

Redesigned account settings improvement

We've also updated the global Paperspace account settings to the latest design system standard. 

You'll now find tabs for Profile, Security, and SSH Keys and in general you should now find it easier to access these important settings.

Dynamic public IP addresses improvement 

  • We added support for dynamic public IP addresses which provide public IP addresses at a bare minimum of cost

Capacity upgrades improvement 

Meanwhile, we've also been busy adding plenty of capacity to Paperspace datacenters.

  • We onboarded a new fleet of RTX4000 machines to the CA1 region
  • We dramatically expanded GPU compute capacity in the NY2 region
  • We added nearly 100TB in shared storage across regions
  • And don't worry, we didn't forget about Europe! New capacity is coming soon!

Bugfixes fix 

  • We fixed a bug that was sometimes causing utilization graphs to display inaccurately



Introducing 100% self-serve private networks, shared drives, and public IPs! πŸ„

We just made a number of improvements to help Core power users self-serve Paperspace resources. 

With this update, you can now create private networks, spin-up shared drives, and assign public IP addresses to any machines that you manage!

Self-serve private networks improvement 

First up, we're pleased to bring private networks to all Core users. When you create a private network, you create a shared resource pool for your team that is isolated from every other machine and customer on Paperspace.

Once you create a private network, you can add machines and drives to the network to share with team members.

Be sure to read the docs for more info!

Self-serve private storage improvement 

Next up, we've made it easy to share a drive among multiple Core machines. After you create a shared network, you can spin-up a shared drive and attach it to the network in a matter of seconds!

For more information on shared drives, check out the docs!

Self-serve public IPs improvement 

Finally, we've made it a lot easier to claim and assign public IP addresses! While previously it was possible to assign a machine to a public IP after the machine was created, we've now streamlined the process to make it more visible at the team level.

To claim a public IP, simply visit the Public IPs tab in the console and claim the address. (Note that Public IPs are region-specific.)

To assign the new public IP to a machine, all we need to do is use the Assign feature to select the machine we want to expose to the public web. That's all there is to it!

If you get stuck please read the docs to learn more or reach out to us with any questions. 

Bugfixes fix 

  • We resolved a troublesome issue that resulted in erroneous invoices being sent to a small number of users
  • We decreased errors related to over-provisioning on the Paperspace public cluster
  • We improved the strategy for guaranteeing hot nodes and faster startup times on the Paperspace public cluster
  • We fixed a number of small issues related to Windows 10 BYOL machines

All-new high-powered NVIDIA Ampere instances! πŸ”‹

We're pleased to announce a series of new GPU-backed instances available on both Core and Gradient featuring NVIDIA's Ampere microarchitecture!

Introducing all-new Ampere instances! announcement 

Announced in mid-2020, Ampere is the codename for NVIDIA's latest line of GPU accelerator cards. Competition for these cards has been fierce and we're happy to bring you four flavors of Ampere, anchored by the top-of-the-line A100.

Introducing Ampere instances

In addition to the instances listed, we've also introduced 2-way, 4-way, and 8-way configurations for these cards. 

The full table of instances on Paperspace has been updated in the docs. In general, any instance made available on Core will arrive in Gradient shortly thereafter.

Multi-GPU also comes to Windows machines improvement  

One thing you might have noticed already is that multi-GPU instances in Core are no longer exclusive to Linux. You can now spin-up any multi-GPU instance on a Windows machine!

Check out the Paperspace console to get started. 

Model-backed deployments in Gradient Deployments improvement  

We added an important feature to Gradient Deployments: model-backed deployments! 

Gradient Deployments

It's now possible to inject a model at deployment runtime which means Gradient is now able to fetch a model from the Gradient model registry directly. Models can also be referenced from an external S3 bucket.

For more information, read the docs or reach out if you'd like a demo!

State persistence bugs in Gradient Notebooks improvement  

We made substantial improvements to the way that application and cell state is managed in Gradient Notebooks. 

Previously, if you navigated away from a notebook while a cell was running and then returned to the notebook, the cell would sometimes lose its state. We're happy to have implemented a substantial fix to this issue and a number of other issues influencing state management.

If you have feedback for us, please drop us a line!

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


New instance types across Core 🐣

We've added RTX4000 and RTX5000 instances to CA1 and NY2 regions, as well as multi-GPU instances for Linux, and new low-cost CPU-only instances for Windows!

Introducing RTX4000 and RTX5000 announcement 

We're pleased to announce RTX4000 and RTX5000 instances are now generally available! 

These cards are based on NVIDIA's Turing microarchitecture and are more than 40% faster than their Pascal series counterparts.

Try RTX

Multi-GPU instances now available on Linux! announcement 

You can now access multi-GPU instances across all regions when selecting Linux as your OS!

P5000x2 instances start at $1.56/hr while P6000x2 instances start at $2.20/hr. 

Try multi-GPU


Low-cost Windows instances now available improvement 

We solidified CPU-only offerings for Windows instances and now provide C5 - C10 instances at an affordable hourly rate.

For just $0.08/hr you can run a full Core VM in the cloud!


Other Improvements

  • We improved our backend error monitoring capabilities giving us substantially more insight into performance degradation and remediation
  • We accelerated our equipment purchasing plan to provide new hardware faster to meet demand
  • We re-wrote some business logic around storage capacity to be able to deliver much faster upgrades


Show Previous EntriesShow Previous Entries