From: Daniel da Veiga <danieldaveiga@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] 10, 100, or 1000mbps uplink?
Date: Fri, 17 Jul 2009 15:24:55 -0300 [thread overview]
Message-ID: <342e1090907171124j265e6b02l45b1e0fb33b6558b@mail.gmail.com> (raw)
In-Reply-To: <49bf44f10907170948n4fc1f2b7ida35fe79b1d506a4@mail.gmail.com>
On Fri, Jul 17, 2009 at 13:48, Grant<emailgrant@gmail.com> wrote:
> I'm about to sign up for a new remote dedicated system and I'm
> wondering if I should spring for the 100mbps or 1000mbps uplink
> upgrades from 10mbps? Is there a test I can run to find out? I'm
> running a lightweight website with maybe 300-400 visitors/day.
>
Most providers will have some sort of tools to monitor your traffic.
Go for 10Mbps, and if you notice slowdown, or the mentioned tools
report bandwidth problems, upgrade... My guess is 10Mbps is a lot for
300-400 unique hits per day, but if you serve downloads too, then you
may have problems in the future, as Kyle said...
--
Daniel da Veiga
next prev parent reply other threads:[~2009-07-17 18:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 16:48 [gentoo-user] 10, 100, or 1000mbps uplink? Grant
2009-07-17 17:44 ` Neil Walker
2009-07-17 17:51 ` Kyle Bader
2009-07-17 18:24 ` Daniel da Veiga [this message]
2009-07-18 15:54 ` Grant
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=342e1090907171124j265e6b02l45b1e0fb33b6558b@mail.gmail.com \
--to=danieldaveiga@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