Contention ratio of shared CPUs on App Platform

I am considering upgrading to a package with a dedicated CPU, but would like to know what the contention ratio is of shared CPU packages.

I am extracting some information from PDF files and it sometimes ends up taking more than a minute depending on the size of the file.

What performance gains could I expect?

Submit an answer
Answer a question...

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Bobby Iliev
Site Moderator
Site Moderator badge
February 9, 2022


The exact performance gains would really depend on your use case. What I would personally do is to start two Droplets, one with a shared CPU and one with a dedicated CPU, and run some tests with my specific application.

Here is some more information that might be helpful:

Dedicated CPU Droplets have guaranteed access to the full hyperthread at all times.

With shared CPU Droplets, the hyperthread allocated to the Droplet may be shared between multiple other Droplets.

When a shared CPU Droplet experiences heavier load, the hypervisor dynamically allocates more hyperthread(s) to it.

However, the amount of CPU cycles available for the hypervisor to allocate depends on the workload of the other Droplets sharing that host.

If these neighboring Droplets have high load, a Droplet could receive fractions of hyperthreads instead of dedicated access to the underlying physical processors.

In practice, this means that shared CPU Droplets can have access to full hyperthreads, but it’s not guaranteed.