public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant <emailgrant@gmail.com>
To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] {OT} dedicated server or cloud server?
Date: Fri, 14 Dec 2012 14:14:13 -0800	[thread overview]
Message-ID: <CAN0CFw04k3bLewMMsK+hiDqmwPeryesKybfA4FozOPLo-8jH3g@mail.gmail.com> (raw)
In-Reply-To: <20121214152403.6ad0160c@khamul.example.com>

[-- Attachment #1: Type: text/plain, Size: 1810 bytes --]

> > > > Would everyone here be in favor of a dedicated server over a cloud
> > > > server from a host with good cloud infrastructure?  The cloud
> > > > server concept is amazing but from what I'm reading a dedicated
> > > > server at the same price point far outperforms it.
> > > >
> > > > - Grant
> > >
> > > Last time I did the calculation, a dedicated or normal virtualized
> > > infrastructure was more cost effective as long as you could
> > > accurately predict the performance you need.
> > >
> > > Cloud services only really help if you need a high dynamic range
> > > regarding scale and performance, e.g. a service that could get a
> > > lot of new users very fast or is only really active for short time
> > > spans.
> >
> > Doesn't a good cloud server also have potentially higher availability
> > compared to dedicated?
>
> Potentially? Yes.
>
> In reality? No.
>
> It's not the virtualization that breaks, it's all the surrounding
> infrastructure, especially Layer 2. You will not believe how fragile
> that stuff can get.
>
> In the old days, a small slip up could isolate a small part of the
> network. These days, a small slip-up easily ripples though the entire
> network and takes down all of it, and sadly this is not rare. The
> networking needs of VMs are radically different from the traditional,
> and this is the side-effect: fragility.

Sounds like the technology isn't ready to compare favorably with dedicated
yet in an "ordinary" scenario with a website to run.  Maybe in a few years?
 The concept is amazing.  I'd also like to move my desktops and even
laptops to the cloud once things get solidified. Then client hardware
becomes interchangeable, disposable... each physical location would only
need one thin client and a bunch of USB peripherals (DisplayLink, etc).

- Grant

[-- Attachment #2: Type: text/html, Size: 2206 bytes --]

  parent reply	other threads:[~2012-12-14 22:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-14  7:49 [gentoo-user] {OT} dedicated server or cloud server? Grant
2012-12-14  8:56 ` Florian Philipp
2012-12-14 10:00   ` Grant
2012-12-14 13:24     ` Alan McKinnon
2012-12-14 13:58       ` Bruce Hill
2012-12-14 22:14       ` Grant [this message]
2012-12-14 13:24     ` Kevin Chadwick
2012-12-14 16:34     ` Florian Philipp
2012-12-14 18:15       ` Kevin Brandstatter
2012-12-14 12:39 ` Bruce Hill
2012-12-14 13:19   ` Alan McKinnon
2012-12-14 13:54     ` Bruce Hill

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAN0CFw04k3bLewMMsK+hiDqmwPeryesKybfA4FozOPLo-8jH3g@mail.gmail.com \
    --to=emailgrant@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox