From: | Jason DiCioccio <jd(at)ods(dot)org> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | Josh Livni <josh(at)umbrellaconsulting(dot)com>, SF Postgres <sfpug(at)postgresql(dot)org> |
Subject: | Re: Recommended/Not Recommended Hosts? |
Date: | 2009-12-10 19:55:11 |
Message-ID: | f372a76b0912101155t29d3715axa00032a507cc3536@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | sfpug |
On Thu, Dec 10, 2009 at 11:20, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> On EC2, other VMs on the same hardware are permitted to "steal" portions
> of the CPU which are allocated to you. So at any given time, you may
> have as little as 50% of the CPUs you're being billed for. And, when
> CPU availability is fluctuating up and down (as it does on EC2), real
> throughput tends to be based on the slowest second rather than peak
> availablity. Most Linux apps, especially databases, do quite poorly
> with erratic resource availability.
Just to clarify, Joyent does this too, no? Or is it just that the
Solaris scheduler handles the prioritization of tasks/resources
better? I haven't yet had the chance to use Joyent, but I thought
this was one of their selling points.
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Mayer | 2009-12-10 19:56:58 | Re: Recommended/Not Recommended Hosts? |
Previous Message | Jon Asher | 2009-12-10 19:54:00 | Re: Recommended/Not Recommended Hosts? |