of course, this requires the other end to support it, which it probably doesn't.
I've also considered selling "multipath vpn" service... the idea being that people with two DSL providers (and one dsl and one cable) provider would setup their gateway (or use a linux box that I sell them and manage) to send all packets out VPNs on both connections, to my own vpn endpoint in a datacenter. The idea being that then my server on the other end of that connection would take the first packet and send it on to it's destination. Assuming that my datacenter has a good connection, you would suffer less packet loss, and less latency.
My solution here would solve the problem if the problem is latency/loss on your last mile connection. It would not help at all if the problem was further along the connection, while multipath-tcp would
and a business. Sure, if I hire a company to build me a wall and it turns out faulty, I'm going to want/the company/ to come fix it, or at least give me a refund.
However, if I hire a company to build me a wall, I will pay substantially more than the wages of the person doing the building plus the cost of materials. And the employee who built the wall? He or She is going to get paid either way. Of course, if they continue to screw up, they will miss out on promotions/raises and/or will get fired. But they will get paid for the time they worked up until they get fired.
In my jurisdiction, withholding/employee/ wages is extremely illegal. Sure, you can fire under-performers, but you've gotta pay them for the hours they worked.
This is a huge part of the difference between being an employee and being a company. Who takes the risk?
yeah, the advantage of bcache is that it will automatically cache the stuff you use often (which yes, can be a disadvantage, too) - I'm just thinking for something like a database server (not that I'd use bcache in a prod database server until it was more stable and until it supported mirroring the SSD) you have large files where parts of the file need caching and other parts of the file don't. A block cache helps with that more than manually symlinking files.
Probably the best programmer I know outright states that he can't productively code for more than four hours a day; but he gets more done in those four hours than most people can do in a week.
If you outright tell people to work for 10-11 hours a day, first your good programmers will all leave. Next, those who can't immediately get better jobs will take long lunches, show up a little late and leave a little early. If you enforce time in-seat somehow, you will have more and more people spending time on slashdot or facebook.
it doesn't do much for I/O. ionice, a much newer program does something similar to what 'nice' does for CPU for I/O intensive tasks. It's pretty good, not as good as nice is for cpu-bound tasks, but eh.
is that while my co-author and I split 15% of the wholesale price (about half the cover price) on physical books, we get something closer to 50% of any ebook sales... and, I think, if the ebook was bought direct from the publisher, that's 50% of what was paid. So even though e-book sales are a pretty small portion of total book sales, on the last statement I got from my publisher, ebook sales comprised a rather large portion of the money actually paid to me.
I've you've ever been to the sf bay area during rush hour, most commuters would give their left nut for the ability to drive in HOV lanes. This will be/huge/ - the volt, with it's integrated range extending gas engine seems like a better idea than the all-electric leaf, but the market value of a HOV sticker, even without the rebates has got to be five or ten grand.
yeah, uh, honestly, if I were a cellphone retailer, I'd advertise it as a feature, right next to battery life (though I imagine there is an inverse correlation between battery life and transmitter power)
I think the largest difference between exxon and BP is not who owns the company, but who's front yard you are shitting on. the gulf coast has some seriously expensive real-estate, and lots of people in a position to fight back.
as a previous poster said, this sort of thing usually happens to third world, where the victims don't have nearly the power to fight back that the residents of the gulf coast have. If this happened to the California coast, the outcry would be even greater; simply because more powerful people would have been directly harmed.
I think it has more to do with it being a large corporation sh-tting all over our frontyard. I mean, if my business is driving trucks, say, and I don't properly maintain my air pressure and as a result I have a blowout and I run over your minivan, you are going to want me to buy you a new minivan and pay the medical bills, right? and you are probably going to be pretty pissed at me, even if I do manage to pay for all the stuff I broke.
I think it's perfectly reasonable to expect BP to pay to clean up it's/very expensive/ mess, and considering how long it has taken them to even stem the flow, I think some anger is reasonable, too.
This isn't about being anti-british or even anti-corporate. this is about cleaning up after yourself when you make a mess of other people's property.
In my market, Virtualization means that I will run fewer, much larger (I mean, not/big iron/... we're talking dual socket, 16-24 core opterons with 64GiB ram) servers, rather than many smaller servers. The market I rent servers to demands small servers. I can save a lot of money by running one 64GiB, 24 core monster vs 8 8GiB boxes.
I mean, if you even/consider/ cisco gear, that usually means you have lots of other people's money and want a solution that 'just works' - Cisco does not compete on price.
Further, unless you are targeting/very small/ companies where the guy making the decision is the owner, and thus is spending his own money, competing on price is rarely a winning strategy. Corporate decision makers make decisions based on "what is least likely to get me fired if things go south" - joe middle manager is unlikely to get a bonus if he saves a couple million going with a cheaper router that works out well, but he will get fired if he buys the cheap router and it goes poorly. The value proposition of cisco is that if you buy cisco kit and it ends up not working? you are less likely to be blamed. I mean, it's cisco. It's usually pretty good shit, even if it is rather overpriced. Also, that's what everyone else is using, 'best practices' right? if the middle manager follows 'best practices' then he's doing his job, right?
now, the thing about competing on price is that in areas where there is quick innovation, you don't see a lot of companies competing on price, so often you can get pretty good margin while still flying under your competition. this is my niche right now; Sure, no large corp would look at me twice, but small companies do, and price-wise, none of my competitors even want to be thought of as my competitors, which is good for me. There is money to be made competing on price in markets that change quickly; it's just your customers, in that case, are not large corporations that spend other people's money.
but my point is that this is not cisco's niche. Cisco, in fact, probably wants to price it's product higher than the 'consumer grade' ipad. the cisco is 'enterprise grade' and we all know that 'enterprise' is code for 'expensive.'
I think that they get a worse rap than they deserve in the open source world. BTRFS anyone? it's not like they don't contribute at all.
I think the problem is twofold: first, they focus on marketing to the PHB- This is likely to get you a bad reputation amongst the techies, unless you are really careful about it. (hell, look at redhat; they deserve an awesome reputation amongst techies, considering the number of linux people they employ and how much they contribute. they have a mediocre reputation.) Second, Oracle seems to have a bad reputation amongst their Engineering staff, and guess what? we talk.
But overall, Oracle is very helpful towards linux; according to the linux foundation, they are in the top 10 companies contributing towards linux[1] (as measured by the number of changes submitted)
So yeah; I mean, I'm not switching to unbreakable linux any time soon, and they certainly aren't red hat, I do think Oracle's reputation should not be as bad as it is.
But what I was trying to say is that networking under xen is pretty easy for me, as it's just Linux stuff. The times I've had to deal with vmware for clients, I've been frustrated trying to do what I wanted to do with their interface, something obviously designed for windows users. I'm not saying the vmware interface is bad; just that it was designed for a windows user.
half what you are talking about is
on
The Book of Xen
·
· Score: 1
'desktop virtualization' which is another animal entirely. (personally, I think desktop virtualization will suffer the same fate of other recent 'thin client' schemes, but really, it's not my area, so that's just wild speculation.)
Provisioning and mass deployments is something I go into a little bit... but certainly isn't the focus of the book. I firmly believe that it is madness to treat physical and virtual servers differently; you want to use one tool for both. And right now, the best one tool is cobbler/koan.
Re:Oh, you want a nice Xen environment?
on
The Book of Xen
·
· Score: 1
haha. Linode is one of the better providers. they are cheaper than slicehost, but more expensive than I am. According to the latest benchmarks I've seen, though, they beat us all (slicehost, ec2 'small', prgmr.com) in terms of CPU power. (though I'm pretty up front about the fact that I optimize for cheap ram over all else, so the results are unsurprising)
what philosophy do you like?
on
The Book of Xen
·
· Score: 1
Personally, after the age of 25 or so, I started to agree more and more with Paul Graham on the subject
Personally? I would not use the debian Dom0
on
The Book of Xen
·
· Score: 1
DomU works, and should continue to work for the foreseeable future; DomU paravirt ops is upstream, so unless debian goes through extra effort to break xen DomU support, it should Just Work.
I avoid the Debian port of the SUSE port
on
The Book of Xen
·
· Score: 1
of the xen stuff- I've had nothing but trouble with it in testing, and looking, it seems that the debian people aren't particularly interested in helping if you have problems, and if you ask the xen mailing lists, they tell you to ask the debian people. If you want stability, you have to deal with the 2.6.18.8-xen kernel distributed by xen.org, or the 2.6.18-patchedtohellandback kernel distributed by RedHat. (the Suse kernel might be stable, I haven't tried it, but the debian port of the suse kernel that is 2.6.27, man, that sucks. Some people say this is because they took the initial patch and have not been good about importing fixes that suse did.)
I've used both those Linux kernels (the xen.org kernel and the RHEL 5 kernel) quite a lot; my experience has been that the RHEL kernel is slightly less stable, while the xen.org kernel has serious driver deficiencies.
For my current production boxes, I'm using the xen.org 2.6.18 system, and I just buy the exact same hardware every time. (Yay for cheap sata_sil cards!)
Another option, of course, is NetBSD5. After starting on NetBSD 3, and switching to linux for pae and x86_64 support, I'm seriously considering switching back, now that NetBSD5 is starting to look good.
Slashdot Mirror
http://www.multipath-tcp.org/
of course, this requires the other end to support it, which it probably doesn't.
I've also considered selling "multipath vpn" service... the idea being that people with two DSL providers (and one dsl and one cable) provider would setup their gateway (or use a linux box that I sell them and manage) to send all packets out VPNs on both connections, to my own vpn endpoint in a datacenter. The idea being that then my server on the other end of that connection would take the first packet and send it on to it's destination. Assuming that my datacenter has a good connection, you would suffer less packet loss, and less latency.
My solution here would solve the problem if the problem is latency/loss on your last mile connection. It would not help at all if the problem was further along the connection, while multipath-tcp would
and a business. Sure, if I hire a company to build me a wall and it turns out faulty, I'm going to want /the company/ to come fix it, or at least give me a refund.
However, if I hire a company to build me a wall, I will pay substantially more than the wages of the person doing the building plus the cost of materials. And the employee who built the wall? He or She is going to get paid either way. Of course, if they continue to screw up, they will miss out on promotions/raises and/or will get fired. But they will get paid for the time they worked up until they get fired.
In my jurisdiction, withholding /employee/ wages is extremely illegal. Sure, you can fire under-performers, but you've gotta pay them for the hours they worked.
This is a huge part of the difference between being an employee and being a company. Who takes the risk?
I mean, bandwidth, at their scale, has got to be pretty cheap, and raising prices on existing customers? always pisses people off.
Personally, though, this is okay for me; I use the DVDs and I don't stream, so a small discount is welcome.
yeah, the advantage of bcache is that it will automatically cache the stuff you use often (which yes, can be a disadvantage, too) - I'm just thinking for something like a database server (not that I'd use bcache in a prod database server until it was more stable and until it supported mirroring the SSD) you have large files where parts of the file need caching and other parts of the file don't. A block cache helps with that more than manually symlinking files.
with your own hard drive and your own SSD. It'd probably cost less, too. http://bcache.evilpiepirate.org/
Probably the best programmer I know outright states that he can't productively code for more than four hours a day; but he gets more done in those four hours than most people can do in a week.
If you outright tell people to work for 10-11 hours a day, first your good programmers will all leave. Next, those who can't immediately get better jobs will take long lunches, show up a little late and leave a little early. If you enforce time in-seat somehow, you will have more and more people spending time on slashdot or facebook.
it doesn't do much for I/O. ionice, a much newer program does something similar to what 'nice' does for CPU for I/O intensive tasks. It's pretty good, not as good as nice is for cpu-bound tasks, but eh.
If you are doing something non-interactive that uses a lot of I/O, use IOnice. experiment, but I find
ionice -p [pid] -c 2 -n 7
to produce reasonable results.
is that while my co-author and I split 15% of the wholesale price (about half the cover price) on physical books, we get something closer to 50% of any ebook sales... and, I think, if the ebook was bought direct from the publisher, that's 50% of what was paid. So even though e-book sales are a pretty small portion of total book sales, on the last statement I got from my publisher, ebook sales comprised a rather large portion of the money actually paid to me.
I've you've ever been to the sf bay area during rush hour, most commuters would give their left nut for the ability to drive in HOV lanes. This will be /huge/ - the volt, with it's integrated range extending gas engine seems like a better idea than the all-electric leaf, but the market value of a HOV sticker, even without the rebates has got to be five or ten grand.
yeah, uh, honestly, if I were a cellphone retailer, I'd advertise it as a feature, right next to battery life (though I imagine there is an inverse correlation between battery life and transmitter power)
I think the largest difference between exxon and BP is not who owns the company, but who's front yard you are shitting on. the gulf coast has some seriously expensive real-estate, and lots of people in a position to fight back.
as a previous poster said, this sort of thing usually happens to third world, where the victims don't have nearly the power to fight back that the residents of the gulf coast have. If this happened to the California coast, the outcry would be even greater; simply because more powerful people would have been directly harmed.
I think it has more to do with it being a large corporation sh-tting all over our frontyard. I mean, if my business is driving trucks, say, and I don't properly maintain my air pressure and as a result I have a blowout and I run over your minivan, you are going to want me to buy you a new minivan and pay the medical bills, right? and you are probably going to be pretty pissed at me, even if I do manage to pay for all the stuff I broke.
I think it's perfectly reasonable to expect BP to pay to clean up it's /very expensive/ mess, and considering how long it has taken them to even stem the flow, I think some anger is reasonable, too.
This isn't about being anti-british or even anti-corporate. this is about cleaning up after yourself when you make a mess of other people's property.
In my market, Virtualization means that I will run fewer, much larger (I mean, not /big iron/ ... we're talking dual socket, 16-24 core opterons with 64GiB ram) servers, rather than many smaller servers. The market I rent servers to demands small servers. I can save a lot of money by running one 64GiB, 24 core monster vs 8 8GiB boxes.
VoIP handsets. it sounds like this is attempting to be an extension/ technological upgrade of that corporate communications device market.
I mean, if you even /consider/ cisco gear, that usually means you have lots of other people's money and want a solution that 'just works' - Cisco does not compete on price.
Further, unless you are targeting /very small/ companies where the guy making the decision is the owner, and thus is spending his own money, competing on price is rarely a winning strategy. Corporate decision makers make decisions based on "what is least likely to get me fired if things go south" - joe middle manager is unlikely to get a bonus if he saves a couple million going with a cheaper router that works out well, but he will get fired if he buys the cheap router and it goes poorly. The value proposition of cisco is that if you buy cisco kit and it ends up not working? you are less likely to be blamed. I mean, it's cisco. It's usually pretty good shit, even if it is rather overpriced. Also, that's what everyone else is using, 'best practices' right? if the middle manager follows 'best practices' then he's doing his job, right?
now, the thing about competing on price is that in areas where there is quick innovation, you don't see a lot of companies competing on price, so often you can get pretty good margin while still flying under your competition. this is my niche right now; Sure, no large corp would look at me twice, but small companies do, and price-wise, none of my competitors even want to be thought of as my competitors, which is good for me. There is money to be made competing on price in markets that change quickly; it's just your customers, in that case, are not large corporations that spend other people's money.
but my point is that this is not cisco's niche. Cisco, in fact, probably wants to price it's product higher than the 'consumer grade' ipad. the cisco is 'enterprise grade' and we all know that 'enterprise' is code for 'expensive.'
I think that they get a worse rap than they deserve in the open source world. BTRFS anyone? it's not like they don't contribute at all.
I think the problem is twofold: first, they focus on marketing to the PHB- This is likely to get you a bad reputation amongst the techies, unless you are really careful about it. (hell, look at redhat; they deserve an awesome reputation amongst techies, considering the number of linux people they employ and how much they contribute. they have a mediocre reputation.) Second, Oracle seems to have a bad reputation amongst their Engineering staff, and guess what? we talk.
But overall, Oracle is very helpful towards linux; according to the linux foundation, they are in the top 10 companies contributing towards linux[1] (as measured by the number of changes submitted)
So yeah; I mean, I'm not switching to unbreakable linux any time soon, and they certainly aren't red hat, I do think Oracle's reputation should not be as bad as it is.
[1]http://www.linuxfoundation.org/publications/whowriteslinux.pdf
is that it's too full of exploitable security holes. I don't run flash (or accoread) on security sensitive computers myself.
seems like paypal would be better off saying so up front; My first reaction was that it was likely more of paypals seemingly racist 'fraud prevention'
yeah, they went over the 'citrix xen' chapter.
But what I was trying to say is that networking under xen is pretty easy for me, as it's just Linux stuff. The times I've had to deal with vmware for clients, I've been frustrated trying to do what I wanted to do with their interface, something obviously designed for windows users. I'm not saying the vmware interface is bad; just that it was designed for a windows user.
'desktop virtualization' which is another animal entirely. (personally, I think desktop virtualization will suffer the same fate of other recent 'thin client' schemes, but really, it's not my area, so that's just wild speculation.)
Provisioning and mass deployments is something I go into a little bit... but certainly isn't the focus of the book. I firmly believe that it is madness to treat physical and virtual servers differently; you want to use one tool for both. And right now, the best one tool is cobbler/koan.
haha. Linode is one of the better providers. they are cheaper than slicehost, but more expensive than I am. According to the latest benchmarks I've seen, though, they beat us all (slicehost, ec2 'small', prgmr.com) in terms of CPU power. (though I'm pretty up front about the fact that I optimize for cheap ram over all else, so the results are unsurprising)
Personally, after the age of 25 or so, I started to agree more and more with Paul Graham on the subject
DomU works, and should continue to work for the foreseeable future; DomU paravirt ops is upstream, so unless debian goes through extra effort to break xen DomU support, it should Just Work.
of the xen stuff- I've had nothing but trouble with it in testing, and looking, it seems that the debian people aren't particularly interested in helping if you have problems, and if you ask the xen mailing lists, they tell you to ask the debian people. If you want stability, you have to deal with the 2.6.18.8-xen kernel distributed by xen.org, or the 2.6.18-patchedtohellandback kernel distributed by RedHat. (the Suse kernel might be stable, I haven't tried it, but the debian port of the suse kernel that is 2.6.27, man, that sucks. Some people say this is because they took the initial patch and have not been good about importing fixes that suse did.)
I've used both those Linux kernels (the xen.org kernel and the RHEL 5 kernel) quite a lot; my experience has been that the RHEL kernel is slightly less stable, while the xen.org kernel has serious driver deficiencies.
For my current production boxes, I'm using the xen.org 2.6.18 system, and I just buy the exact same hardware every time. (Yay for cheap sata_sil cards!)
Another option, of course, is NetBSD5. After starting on NetBSD 3, and switching to linux for pae and x86_64 support, I'm seriously considering switching back, now that NetBSD5 is starting to look good.