Increase the RAM of the demo machine
-
@girish feel free to use my referral code if you do: trimurl.co/ssd
-
We got a server on ssdnodes (48GB RAM) but looks like CPU is like very very very slow. It takes forever to unzip docker images. Let's see if the situation improves.
-
@girish sometimes you get on an overprovisioned box, just ask to have it moved to a less busy node.
-
So far, the performance on ssdnodes has been super flaky. I won't use it for anything production related because it seems to become really really slow every other day. And one can request a change of host only so many times...
@girish said in Increase the RAM of the demo machine:
the performance on ssdnodes has been super flaky.
Given their too good to be true pricing (and lots of others out there giving similar negative reviews) this doesn't surprise me one bit.
-
After some back and forth with their support, they can be coaxed into letting you know that the machine you've moved to is locked, ie won't be getting new customers.
They do have some issues figuring out IO starvation issues, which are obvious. Higher quality support would do them good.
My system was fine for a long while until recently due to IO starvation.
Frankly I had forgotten about this, since it's been ok for so long. Had to relearn that lesson.
# dd if=/dev/zero of=/tmp/test1.img bs=1G count=1 oflag=dsync ; rm /tmp/test1.img 1+0 records in 1+0 records out 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 5.93197 s, 181 MB/s
As long as there's IO, it'll do.
-
After some back and forth with their support, they can be coaxed into letting you know that the machine you've moved to is locked, ie won't be getting new customers.
They do have some issues figuring out IO starvation issues, which are obvious. Higher quality support would do them good.
My system was fine for a long while until recently due to IO starvation.
Frankly I had forgotten about this, since it's been ok for so long. Had to relearn that lesson.
# dd if=/dev/zero of=/tmp/test1.img bs=1G count=1 oflag=dsync ; rm /tmp/test1.img 1+0 records in 1+0 records out 1073741824 bytes (1.1 GB, 1.0 GiB) copied, 5.93197 s, 181 MB/s
As long as there's IO, it'll do.
@robi said in Increase the RAM of the demo machine:
they can be coaxed
To me this is just proof that their standard service is rubbish and they should be avoided.
If you have to coax them into providing the service they claim to be providing they evidently are not providing said service.
Each to their own I guess but I wouldn't touch them with a barge pole.
-
@nebulon perhaps a time to consider using one of the large memory instances from SSD Nodes or Contabo for the same pricing.
@robi I love you for this post!
-
@robi I love you for this post!
-
@LoudLemur and @robi just to add here the option to run
hdparm -Tt /dev/<youdisk>
, which will measure a few things for disk I/O.@nebulon said in Increase the RAM of the demo machine:
@LoudLemur and @robi just to add here the option to run
hdparm -Tt /dev/<youdisk>
, which will measure a few things for disk I/O.That requires
root
and for hdparm to actually be available and installed.Hence I use:
dd if=/dev/zero of=/tmp/test1.img bs=1G count=1 oflag=dsync ; rm /tmp/test1.img