Does my Dedicated CPU plan run an SSD?
Just moved from a Linode 16GB (6 core + SSD) to a Dedicated CPU 16GB (8 core). I've got processes that run a few times per day that are intensive all around, but run at a very consistent pace, and now they're running at about half speed. Best I can tell so far is that disk I/O is my bottleneck. cat /sys/block/sda/queue/rotational returns 1, so does lsblk -d -o name,rota. Linode folks- are you able to confirm for me that I'm still on an SSD or not?
Thanks!
3 Replies
I understand that I'll lose some CPU burst as I won't be stealing from others, but I'm assuming disk I/O shouldn't be affected (and that stealing wouldn't have been doubling my effective CPU).
Hi,
I'm not a Linode staff member, but here's some things I ran into when using a dedicated CPU plans, and a couple suggestions.
The dedicated CPU plans do indeed have SSD's, as far as I know. However, some specs I received indicated that a prior nanode plan I had actually ran on a CPU that was faster in clock speed than the CPU I have on my current dedicated plan.
My previous nanode plan had an Intel Xeon CPU E5-2680 v2 running at 2.8GHZ. The first host I landed on for my dedicated CPU plan ran an AMD EPYC 7501 at 2.0GHZ. Due to a specific use case in which Intel performed better than AMD for me, I was able to have my dedicated CPU Linode migrated to a machine running an Intel Xeon CPU E5-2697 v4 at 2.2GHZ. Sometimes Intel will perform better than AMD, and I'm sure the reverse is also true.
It is also possible that you're contending with others using disk I/O, as you only have the CPU to yourself on these particular plans. You could open a support ticket with Linode and see if they could migrate you to a different host. If you're on AMD, you could try an Intel host and see if that works better for you, or try the reverse if you're on an Intel host. You aren't guaranteed a host running a particular CPU type as in Intel or AMD, though, and if you do migrate, I'd recommend doing so as soon as possible, due to the fact that resources on the selected host might be reallocated to another Linode before you can complete the migration yourself, should you wait.
Blake