From: kashani <kashani-list@badapple.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: How to record memory usage & bandwidth usage?
Date: Tue, 25 Oct 2011 18:52:22 -0700 [thread overview]
Message-ID: <4EA767D6.4060303@badapple.net> (raw)
In-Reply-To: <CAA2qdGVwo1dE4B+3Lwf-_0yvRp6ctSMCtGXAwm5Z=C6Od1334w@mail.gmail.com>
On 10/25/2011 6:27 PM, Pandu Poluan wrote:
> (Sorry for the late reply; somehow this thread got lost in the mess)
>
> On Oct 12, 2011 2:03 AM, "James" <wireless@tampabay.rr.com
> <mailto:wireless@tampabay.rr.com>> wrote:
> >
> > Pandu Poluan <pandu <at> poluan.info <http://poluan.info>> writes:
> >
> >
> > > The head honcho of my company just asked me to "plan for migration of
> > > X into the cloud" (where "X" is the online trading server that our
> > > investors used).
> >
> > This is a single server or many at different locations.
> > If a WAN monitoring is what you are after, along with individual
> > server resources, you have many choices.
> >
>
> It's a single server that's part of a three-server system. The server
> needs to communicate with its 2 cohorts continuously, so I have to
> provision enough backhaul bandwidth from the cloud to my data center.
>
> In addition to provisioning enough RAM and CPU, of course.
>
> > > Now, I need to monitor how much RAM is used throughout the day by X,
> > > also how much bandwidth gets eaten by X throughout the day.
> >
> > Most of the packages monitor ram as well as other resource utilization
> > of the servers, firewall, routers and other SNMP devices in your network.
> > some experimentation may be warranted to find what your team likes best.
> >
>
> Currently I've settled on a simple solution: run dstat[1] with nohup 30
> minutes before 1st trading session, stop it 30 minutes after 2nd trading
> session, and send the CSV record via email. Less intrusion into the
> system (which the Systems guys rightly have reservations of).
>
You're not going to be happy with this design for a couple of reasons.
1. It's more expensive that your current setup. If the two servers at
your datacenter are down I assume the server is the cloud is useless and
vice versa. You already have to maintain infrastructure for those two
servers so you're realizing no savings by eliminating on server from
your infrastructure. Buying a $1500 rack server amortized over three
years is a better deal than paying for equivalent power in the cloud.
2. Latency. You're increasing it.
3. Cloud performance varies. Networks split, machines run slow, it
happens. You'll have more consistent performance on your own machines.
It's getting better, but it's still something with which to be aware.
Migrating to virtual servers makes some sense, but you need to look at
it on a case by case basis.
kashani
next prev parent reply other threads:[~2011-10-26 1:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 9:48 [gentoo-user] How to record memory usage & bandwidth usage? Pandu Poluan
2011-10-11 10:21 ` Mick
2011-10-11 10:35 ` Matthew Marlowe
2011-10-11 18:05 ` [gentoo-user] " James
2011-10-26 1:27 ` Pandu Poluan
2011-10-26 1:33 ` Pandu Poluan
2011-10-26 1:52 ` kashani [this message]
2011-10-26 2:31 ` Pandu Poluan
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=4EA767D6.4060303@badapple.net \
--to=kashani-list@badapple.net \
--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