• Announcements

    • MannDude

      Current state of vpsBoard   02/04/2017

      Dear vpsBoard members and guests:

      Over the last year or two vpsBoard activity and traffic has dwindled. I have had a change of career and interests, and as such am no longer an active member of the web hosting industry.

      Due to time constraints and new interests I no longer wish to continue to maintain vpsBoard. The web site will remain only as an archive to preserve and showcase some of the great material, guides, and industry news that has been generated by members, some of which I remain in contact to this very day and now regard as personal friends.

      I want to thank all of our members who helped make vpsBoard the fastest growing industry forum. In it's prime it was an active and ripe source of activity, news, guides and just general off-topic banter and fun.

      I wish all members and guests the very best, whether it be with your business or your personal projects.

      -MannDude

michyprima

Members
  • Content count

    8
  • Joined

  • Last visited

Community Reputation

2 Neutral

About michyprima

  • Rank
    Registered Lurker
  1. Aruba Cloud: Choosing the correct size

    That's great but even if you don't mind the current look it doesn't mean we should stop improving it ;) Having a technical rep directly on the forum may be a good thing in case someone needs help doing something I guess. I'm glad you haven't had any problems but I also know no system is perfect :)
  2. Aruba Cloud: Choosing the correct size

    No problem! System Info ----------- Processor : Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz CPU Cores : 1 Frequency : 2299.998 MHz Memory : 993 MB Swap : 951 MB Uptime : 4 days, 2:18, OS : Ubuntu 14.04.4 LTS Arch : x86_64 (64 Bit) Kernel : 3.13.0-83-generic Hostname : xxx Speedtest (IPv4 only) --------------------- Your public IPv4 is xxx Location Provider Speed CDN Cachefly 43.3MB/s Atlanta, GA, US Coloat 15.8MB/s Dallas, TX, US Softlayer 12.2MB/s Seattle, WA, US Softlayer 9.39MB/s San Jose, CA, US Softlayer 9.83MB/s Washington, DC, US Softlayer 16.8MB/s Tokyo, Japan Linode 8.56MB/s Singapore Softlayer 6.02MB/s Rotterdam, Netherlands id3.net 40.2MB/s Haarlem, Netherlands Leaseweb 73.3MB/s Disk Speed ---------- I/O (1st run) : 739 MB/s I/O (2nd run) : 1.0 GB/s I/O (3rd run) : 1.1 GB/s Average I/O : 247.033 MB/s Looking at the avg I/O I can see why you call this script flawed - 247 is definitely not the average between the three runs! :P Edit: looking at the bash script, I see why it's failing: it does not check if values are GB or MB, so threats 1.0 GB/s like it was 1.0 MB/s. I would also never alter the results of my tests. I know this is just my word and I'm no one, but hey, my ethics are pretty rigid on that :)
  3. Aruba Cloud: Choosing the correct size

    I respect everybody's opinion, and as you noticed, I prefer discussions over public attacks :) Latency was measured from datacenter1 in Arezzo, Italy. Another test: ** SIEGE 3.0.5 ** Preparing 500 concurrent users for battle. The server is now under siege… Lifting the server siege… done. Transactions: 197955 hits Availability: 99.98 % Elapsed time: 599.75 secs Data transferred: 449.12 MB Response time: 1.50 secs Transaction rate: 330.06 trans/sec Throughput: 0.75 MB/sec Concurrency: 493.83 Successful transactions: 197955 Failed transactions: 39 Longest transaction: 31.54 Shortest transaction: 0.33 I accepted to stand behind this product because I like it and because it's actually quite good. There really aren't many VPS products with those specs capable of serve almost 500 users (we are still talking about static pages over nginx) I also did not "run" as I'm still here. I run a couple of those VPS myself and I can run some more (non-destructive ;)) benchmarks if you want me to.
  4. Aruba Cloud: Choosing the correct size

    I'll leave here some numbers from the full review I wrote, which is in italian and obviously wouldn't have fitted here: linux 4.4.2 make time 149m29, command used: make -j2 vpsbench: CPU model: Intel(R) Xeon(R) CPU E5-2650L v3 @ 1.80GHz Number of cores: 1 CPU frequency: 1799.999 MHz Total amount of RAM: 993 MB Total amount of swap: 951 MB System uptime: 1:31, I/O speed: 721 MB/s Bzip 25MB: 8.36s Download 100MB file: 69.8MB/s Network speed tests: Europe: 70MB/s USA: 30MB/s Asia: 10MB/s (replication urls are in the review) Latency tests: 8.8.8.8: 7.774 ms DC1<->DC1: 0.745 ms tim.it: 14.808 ms 108.61.5.91 (USA): 100.448 ms 150.101.135.3 (Australia): 324.774 ms 106.187.96.148 (Giappone): 285.020 ms google.it: 17.327 ms nvidia.com: 172.901 ms Let me know if you are interested in having a look in the full review, as I don't want to spam my blog if it's not needed :-) While for someone experienced like you my write may look useless, for starters I still think it will be different. You don't need any experience to approach VPS machines. It's quite the opposite: practicing on a real VPS, facing real problems, building something satisfying for you it's actually a nice way to start. Experience will come as you learn how to get past problems so, when you learnt the basics, you can actually leave shared hosting and open yourself to a new world.
  5. When should you use SSL?

    I prefer using SSL whenever I could, because of HTTP2, but I avoid using SSL for wide-audiences websites if it's not strictly needed (i.e. storing user data, processing payments etc) because there are still lots of clients out there not using SNI (Die XP, die!) and it would require you having a different IP address for each website and that's simply a waste of resources most of the times. My blog, as an example, is a personal site, runs on SSL+HSTS, and I couldn't care less if it weren't available to someone, as it's just a blog. My company's main website, on the other end, is running on the same VPS, has SSL, but I configured nginx to serve its cert first if the client is not using SNI. Another option is to use a single SSL cert for all websites, using wildcard certificates and/or multiple domains certificates but that may turn up expensive.
  6. Which domain i should start with ?

    If I were you I'd start with X3, then use a redirect if I changed my mind and wanted a change. I'd suggest avoiding anything in the name like "super", "best", "ultra" etc as those prefixes make the whole service look childish.
  7. Aruba Cloud: Choosing the correct size

    While I may see your point, I don't think I actually did something so bad as you picture it. There still is a considerable amount of informations in the first post; someone starting from the ground obviously has no idea how much resources needs a daemon or another and the estimator I wrote is obviously valid for every provider out there.
  8. Approaching to the unmanaged world is not always easy, and it's definitely hard, for a newbie, realize how many resources he will need for his setup. We have lot of variables but I'm pretty confident that, after reading this, you will have a better idea of your needs. Exactly like a normal PC a VPS has some RAM, bandwidth, CPUs and so on. But how much of them do I need? Those are the sizes offered by the company, starting from €1: arubacloud.com Let's start from the classical use: the web server. I actually like more nginx than apache, because it uses much less resources, and soon you'll see why. A web server, usually has three components: an HTTP server (nginx in our case) a dynamic pages engine (PHP) the database server (MySQL) You can live without the last two if, obviously, you intend to only serve static pages. Yes, that means no wordpress! In this case, the size S will be more than enough because nginx, with those resources, can easily serve hundreds of people simultaneously. If you want or need php and sql, then it will be a pretty different story. You will need to choose your size on how much traffic you expect to have. You will need 200MB of RAM for MySQL, another hundred for nginx, and half hundred for each PHP process. For a website with a few thousands requests per day, the S will still be enough. From this point on, however, you should monitor your average CPU usage; if this is approaching or already is 100%, you will need to choose an L to get another core, otherwise an M will do the trick. Let's now talk about mail servers. A mail server usually haves: an SMTP server (postfix) an IMAP server (POP3? nah...) a daemon scanning for spam and viruses eventually, a MySQL database storing users and other data I can already say you will need lots of RAM for this. My tests revealed that a VPS with postfix, dovecot and amavis, has more or less an hundred MB of free RAM from a total of 1024. The virus scanner uses lots of ram and, avoiding it, you can save a lot. Optimizing your setup you could be able to also fit MySQL on an S, but I discourage doing so. If you need a webserver and a mailserver, my advice is to get two Ss, so you can split the load between the two, and keep MySQL with the webserver, which is obviously a more efficient setup. This kind of setup can tolerate 25-50 users simultaneusly. For both use-cases, however, the XL is a nice choice if you have a business to build up on webservices like small hosting or mail hosting or you think you will have lots of active users. It's very hard to spend all the resources this size offers, especially if your setup is correctly done.