We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
HDD VS SSD
HDD VS SSD
Hey everyone,
At this moment we are running an SSD VPS (300GB) (59GB used)
[*] 12GB RAM (2GB used)
[*] Four Cores
With VestaCP. But we think it's a little bit overkill. Since we are running about 20 websites on it.
So we want to run it on another VPS with these specs
[*] 6 GB RAM
[*] Two Cores
[*] 500GB HDD
I am concerned with is the use of an HHD instead of an SSD (since many websites of our MariaDB and an HDD use the computing power of MariaDB).
Since most of our websites are running on Wordpress (On the other hand, the WordPress websites are cached).
What is your opinion about this?
using NGINX + APACHE + VSFTPD + EXIM + Dovecot + spamassasin + iptables + fail2ban and DNS (+file quota)
Specs
CPU
Memory
DISK
At this moment we are running an SSD VPS (300GB) (59GB used)
[*] 12GB RAM (2GB used)
[*] Four Cores
With VestaCP. But we think it's a little bit overkill. Since we are running about 20 websites on it.
So we want to run it on another VPS with these specs
[*] 6 GB RAM
[*] Two Cores
[*] 500GB HDD
I am concerned with is the use of an HHD instead of an SSD (since many websites of our MariaDB and an HDD use the computing power of MariaDB).
Since most of our websites are running on Wordpress (On the other hand, the WordPress websites are cached).
What is your opinion about this?
using NGINX + APACHE + VSFTPD + EXIM + Dovecot + spamassasin + iptables + fail2ban and DNS (+file quota)
Specs
CPU
Code: Select all
top - 19:37:28 up 35 days, 6:58, 0 users, load average: 0.05, 0.10, 0.17
Tasks: 122 total, 2 running, 120 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.0 us, 0.0 sy, 0.0 ni, 96.9 id, 0.0 wa, 0.0 hi, 0.0 si, 3.1 st
KiB Mem : 12138964 total, 9492152 free, 1706680 used, 940132 buff/cache
KiB Swap: 0 total, 0 free, 0 used. 9490348 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1 root 20 0 190868 3888 2556 S 0.0 0.0 26:08.85 systemd
2 root 20 0 0 0 0 S 0.0 0.0 0:01.46 kthreadd
3 root 20 0 0 0 0 S 0.0 0.0 0:20.69 ksoftirqd/0
5 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/0:+
7 root rt 0 0 0 0 S 0.0 0.0 0:47.00 migration/0
8 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rcu_bh
9 root 20 0 0 0 0 S 0.0 0.0 21:12.98 rcu_sched
10 root rt 0 0 0 0 S 0.0 0.0 0:10.49 watchdog/0
11 root rt 0 0 0 0 S 0.0 0.0 0:13.78 watchdog/1
12 root rt 0 0 0 0 S 0.0 0.0 0:34.01 migration/1
13 root 20 0 0 0 0 S 0.0 0.0 0:31.72 ksoftirqd/1
15 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/1:+
16 root rt 0 0 0 0 S 0.0 0.0 0:13.68 watchdog/2
17 root rt 0 0 0 0 S 0.0 0.0 0:28.60 migration/2
18 root 20 0 0 0 0 S 0.0 0.0 0:22.35 ksoftirqd/2
20 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/2:+
21 root rt 0 0 0 0 S 0.0 0.0 0:16.39 watchdog/3
22 root rt 0 0 0 0 S 0.0 0.0 0:43.79 migration/3
23 root 20 0 0 0 0 S 0.0 0.0 3:35.61 ksoftirqd/3
25 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/3:+
27 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kdevtmpfs
28 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 netns
29 root 20 0 0 0 0 S 0.0 0.0 0:02.14 khungtaskd
30 root 0 -20 0 0 0 S 0.0 0.0 0:00.01 writeback
31 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kintegrityd
32 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset
33 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kblockd
34 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 md
40 root 20 0 0 0 0 S 0.0 0.0 0:15.36 kswapd0
41 root 25 5 0 0 0 S 0.0 0.0 0:00.00 ksmd
--------------------------------------------------------------------------
--------------------------------------------------------------------------
Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz
Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz
Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz
Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 63
Model name: Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz
Stepping: 2
CPU MHz: 2399.998
BogoMIPS: 4799.99
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 32K
L1i cache: 32K
L2 cache: 4096K
NUMA node0 CPU(s): 0-3
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon rep_good nopl eagerfpu pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt arat
Code: Select all
total used free shared buff/cache available
Mem: 11854 1689 9224 618 940 9241
Swap: 0 0 0
Total: 11854 1689 9224
--------------------------------------------------------------------------
12430 m total memory
1771 m used memory
1792 m active memory
741 m inactive memory
9672 m free memory
47 m buffer memory
938 m swap cache
0 m total swap
0 m used swap
0 m free swap
16516360 non-nice user cpu ticks
16100 nice user cpu ticks
2855238 system cpu ticks
1183440075 idle cpu ticks
2556267 IO-wait cpu ticks
0 IRQ cpu ticks
150977 softirq cpu ticks
12420564 stolen cpu ticks
965997286 pages paged in
1083794753 pages paged out
0 pages swapped in
0 pages swapped out
3250593384 interrupts
695493914 CPU context switches
1513255144 boot time
9035463 forks
--------------------------------------------------------------------------
# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 2.8 present.
Handle 0x1100, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: Unknown
Data Width: Unknown
Size: 12288 MB
Form Factor: DIMM
Set: None
Locator: DIMM 0
Bank Locator: Not Specified
Type: RAM
Type Detail: Other
Speed: Unknown
Manufacturer: QEMU
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Rank: Unknown
Configured Clock Speed: Unknown
Minimum Voltage: Unknown
Maximum Voltage: Unknown
Configured Voltage: Unknown
Code: Select all
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 295G 56G 225G 20% /
devtmpfs 5.8G 0 5.8G 0% /dev
tmpfs 5.8G 0 5.8G 0% /dev/shm
tmpfs 5.8G 617M 5.2G 11% /run
tmpfs 5.8G 0 5.8G 0% /sys/fs/cgroup
/dev/sda1 985M 253M 682M 28% /boot
--------------------------------------------------------------------------
--------------------------------------------------------------------------
Disk /dev/sda: 322.1 GB, 322122547200 bytes, 629145600 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x000e1aae
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 2050047 1024000 83 Linux
/dev/sda2 2050048 629145599 313547776 83 Linux
Re: HDD VS SSD
HDD vs. SSD: Always use SSD, performance is much better. You don't write the pricings of your vps or the hoster. For my company I own some rackspace in a datacenter, also I'm ripe lir member, but we still use some services (vps and dedicated) at hetzner.com.
stay at ssd, dont switch back to hdd!
stay at ssd, dont switch back to hdd!
-
- Support team
- Posts: 1096
- Joined: Sat Sep 06, 2014 9:58 pm
- Contact:
- Os: Debian 8x
- Web: apache + nginx
Re: HDD VS SSD
SSD is generally always better than HDD... no questions on that.
Yet if costs matter, it does depend on hardware config, Raid Controllers, motherboards and more importantly the type of SSD being used. Samsung Enterprise NAND SSDs are much better performer while I've seen good hardware properly configured to work as good as Low-end SSDs.
You can fine tune MySQL to use more RAM (if available) and put transactional tables in memory, which is way faster than any SSD and can even use RamDrive but all this needs extra work and knowledge.
As I already said, in general if you want a no-brainer out of box setup, get SSD. Their failure rate is also considerably less than HDDs so you are safer with Data too.
Good luck
Yet if costs matter, it does depend on hardware config, Raid Controllers, motherboards and more importantly the type of SSD being used. Samsung Enterprise NAND SSDs are much better performer while I've seen good hardware properly configured to work as good as Low-end SSDs.
You can fine tune MySQL to use more RAM (if available) and put transactional tables in memory, which is way faster than any SSD and can even use RamDrive but all this needs extra work and knowledge.
As I already said, in general if you want a no-brainer out of box setup, get SSD. Their failure rate is also considerably less than HDDs so you are safer with Data too.
Good luck
Re: HDD VS SSD
As it seems you are comparing Contabos VPS M vs VPS M SSD I strongly suggest the SSD.
Not only are Contabo cores often spiking for no apparent reason (even on a fresh install) even though its KVM but also the are their HDD not the fastest..at all. Even though it says SSD boosted drives Id still go full SSD.
Not only are Contabo cores often spiking for no apparent reason (even on a fresh install) even though its KVM but also the are their HDD not the fastest..at all. Even though it says SSD boosted drives Id still go full SSD.