LEB/LET benchmarks - vps benchmark 2.x
I'm pleased to announce
- the official start of a series of reviews and benchmarks which I have been asked to do by @jbiloh.
- the availability of a largely new and significantly enhanced version 2.x of my benchmark software vpsbench.
I would have very much liked jbiloh to pick the first provider and product to be reviewed as a small token of appreciation for his commitment and extensive work to make LET great again. However even after (mildly) pushing him he didn't react. Obviously he wants to stay absolutely neutral. While this spoils my little "thank you" plan I can accept and even appreciate his decision to stay away from even just the appearance of not being perfectly neutral.
So instead a heartfelt, sincere "Thank you, Jon Biloh. for investing so much in LEB/LET, for your work, your commitment, and your trust in us" (and for tolerating the beatings you took at the (new) start!).
Well, "32nd of never", as a particularly stubborn jsg hater put it a week or two ago in my interview thread, has arrived (and the wannabe enemy, as usual, is wrong).
vpsbench 2.x is completed and ready to rock
and will be made publicly available in the coming days.
Here is the help page created by "vpsb -h" to give you a first taste:
Usage: vpsb [Options] (see readme for details) and Options are -h or --help for this help -b or --buffdisk runs disk tests buffered instead of sync,direct -c or --cputest run proc/mem test -C or --cpucount=x proc/mem test Rounds (def. 128) -m or --memsize=x proc/mem test mem. Size [MB] (def. 16) -d or --disktest run disk test -D or --diskcount=x disk test rounds (def. 512) -S or --dslicesize=x disk test slice size [MB] (def. 4) -i or --interval=x test interval (ms) -n or --nettest[=TF] run network test (using Target_File) where 'TF' is a target file containing the URLs for benchmarking (def. 'ntargets') -N or --noicmpping do not ICMP ping (which needs root) -p or --dtpath=path path for disk test (def. /tmp) -q or --quiet run quiet, keep stdout clean -s or --sysinfo show system info -v or --version for version info Note that -scdn is assumed by default. Use c, d, n, and s options to only run specific tests.
Besides basically completely rewriting vpsb to make it more modular there is interesting new functionality, too.
First re modular: With v 2.x I can pull out any module, e.g. disk testing, and turn it into it's own executable with very little work. This is particularly helpful as some other benchmarkers (e.g. @poisson) have shown interest in using my code as a "library" in their own (shell based AFAIK) benchmarks.
Disk testing can now be done either in "normal" buffered mode or in direct/sync mode. This point seems small but is quite important. Explanation: As I have repeatedly explained my interest (when creating vpsb) was to test the system that is, e.g. the speed of the disks; even more, I wanted to have a tool to "break through" caching layers. For that direct/sync access is needed. On the other hand, and just as valid, people might be interested in the "what do I get in speed?" question.For that good caching is a plus although it may in most normal use cases hide potentially sub-par hardware.
This is particularly true with linux because linux mercilessly caches disks; in fact I have even seen linux (e.g. 4.1x kernels) simply ignoring direct and sync flags. One often cited official reason for that being that soft logging file systems (e.g. ext4 ) can't support those flags. My personal and subjective impression is that linux is too focussed on it's competing with Windows.
So, it's for good reasons that I will continue to do my benchmarking using FreeBSD because it does honor direct/sync requests which allows a much better insight into the hardware.
Plus, both the processor & memory and the disk tests now allow more fine grained control both of the rounds and the size of a single test round.
Another significant change/enhancement is that vpsb v.2 now also does both a (normal) ping and a "web ping". This allows to better recognize and judge some issues (e.g. ICMP "optimized" routing) and problems (e.g. a slow http server). The (normal) ping which requires the benchmark to run as root can be disabled with a simple switch. In addition the network benchmark module now also shows the http code if it's not 200, so http problems with a target server can be more easily diagnosed.
Announement to providers
A couple of weeks ago a number of providers have announced their interest in being reviewed/benchmarked. The order of my first reviews/benchmarks will be the following:
- First: Those providers should re-contact me (either here or by PM) and I will "choose" the first one to be tested by random out of those re-contacting me. AFAIC the first test can start tomorrow.
- Next: I'll repeat the above random choice (using /dev/urandom as "dices") for the rest of the providers re-contacting me, one by one.
- Others: Providers who contact me (and have not yet contacted me some weeks ago) will be put on my ToDo list and chosen using the same random process.
Please note that I will take the liberty to "insert" reviews/benchmarks of providers of my choice in case I'm particularly interested.
I do not care whether you want a dedi or VPS or VDS and what configuration reviewed/benchmarked. What I do require is min. 256 MB RAM and min 7.5 GB disk space and a convenient way to use or install FreeBSD (min. 12.0). So, I will not (or only as an exception in a few special cases) benchmark/review OpenVZ or linux container VPS.
I offer 2 kinds of reviews/benchmarks, short term and one month. Short term means min. (and typ.)3 days and max. 1 week. The test system will be used only and exclusively for benchmarking. Please be sure to create a test account for me as I usually will not create an account myself just for reviewing/benchmarking you
Feel free to ask if you have any questions I haven't addressed.
There is one last point open: vpsb does show all flags but I'd like to show some particularly important (to you) flags like e.g. obviously 'AES' more prominently. So, please tell me which flags you are particularly interested in.