>From the FAQ: How does the CPU scheduling work?
Each Slice is assigned a fixed weight based on the memory size (256, 512 and 1024 megabytes). So a 1024 has 4x the cycles as a 256 under load. However, if there are free cycles on a machine, all Slices can consume CPU time. This creates a leveraged environment that allows smaller Slices to likely consume cycles as needed, but still protects larger Slices that require higher loads. > On 8/29/07, Petri Laihonen <pietu at weblizards.net> wrote: > > > > Are there any numbers about how many slices are sold out of one server > > (hardware)? > > Can processes on the other slices bog your slice to halt? > > > > Then on the other hand, if you have to pay it upfront, it could mean that > > it buys you one blade out of blade server farm and the cases above cease to > > exist. > > > > Petri > > > > > > > > Shannon Roddy wrote: > > On 8/29/07, Dustin Puryear <dustin at puryear-it.com> wrote: > > > > > > So what's the deal with slicehost? What makes them special? I keep > > hearing about them. > > > > -- > > > > > > In addition to everything Brad said, I can do such things as run > > mailman for a 501(c)3, apache vhosts, run a true mail server, etc. all > > for $20 a month with someone else having to worry about the > > infrastructure. Not a bad deal considering most hosting providers > > charge nearly the same for a whole lot less. Only issue I see with > > them is having to pay up front. > > > > _______________________________________________ > > General mailing list > > General at brlug.net > > http://mail.brlug.net/mailman/listinfo/general_brlug.net > > > > > > > > _______________________________________________ > > General mailing list > > General at brlug.net > > http://mail.brlug.net/mailman/listinfo/general_brlug.net > > > > >
