New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
How do you check single core speed/performance?
ChaoscripT
Member
in General
Hi,
What is the best way to check single core speed/performance?
Regards.
Comments
YABS
wget -qO- yabs.sh | bash
Typical thorough vps and node examination begins from 72 hours long random interval yabs testing. Just cron and hammer vps to the ground. This would shed some light on node overselling, limitations and even technical support.
Next 72 hours there is randomized speed test events to check network and how consistent it is.
For both tasks yabs is sufficient and 144 hours of testing is enough to determine if your 2.99 is well spent.
Cinebench or Geekbench is the best way to check single core speed/performance.
wget -qO- bench.sh | bash
wget -qO- yabs.sh | bash
wget -qO- benchy.pw | sh
just start mining crypto and see how much fat profits you make 🤑🤑🤑🤑🤑🤑
If you're going to use YABS for this, you can disable the disk and iperf tests:
curl -sL yabs.sh | bash -s -- -fi
other than testing it, is there any online database for users to submit the results? so as to compare to other providers or set an estimate
Depends on the server or VPS specs,
If it's ≤ 1 Core and 2GB RAM,
then the best way is Geekbench 5 and Passmark PeformanceTest
If it's ≥ 2 Core and 4GB RAM,
then you could use Geekbench 5 - 6, Passmark PeformanceTest, Cinebench R20 - R23, UnixBench.
Alternatively for more comprehensive testing, you could rely on Phoronix Test Suite (OpenBenchmarking). There are many tests you could choose there.
Of course if you have a particular application in mind, the best test is to load-test that process rather than using an artificial benchmark.
If the code doesn't directly support limiting concurrency for a single-core test, use taskset (https://unix.stackexchange.com/questions/73/how-can-i-set-the-processor-affinity-of-a-process-on-linux ) or your OS's equivalent to constrain it to a specific core. For a web-called application with multiple requests (rather than testing a single long-running process) you may need some config jigger-pokery may be needed to force the web server to accept and bequeath core affinity.
For now I will also rely on YABS solely