I have no problem with Bell slowing down my P2P transfers when there's congestion. However, from experience, Bell throttles based on time and not bandwidth/congestion. As soon as the throttling times are over, the P2P downloads speed up considerably, so it's obviously not throttled based on congestion on the network. As for downloading when it's not affecting others. It would only affect you if they were experiencing congestion, not based on time of day; which is what they have implemented.
Bell is artificially slowing down their customers during certain hours of the day because they are unable to implement a correct solution to handle congestion.
wrt airplane fuel: Actually there are some companies out there that do payload and fuel optimization with knowledge of fuel prices, payload weights, aircraft performance, forecast wind patterns. There is also a cost in flying with more fuel than you need, as it takes fuel to transport fuel to your destination. The algorithms for figuring out how much fuel to put on board aren't particularly difficult (at least when I was working on it) it's just _really_ computationally expensive, and also estimations upon estimations, upon estimations, upon predictions. Another thing to be considered: the way the plane is packed will also adjust the amount of fuel they use. So when you're packing a plane, you've got to deal with weights side to side, and front to back too.
Except for all of the regulations on exactly which flight levels you're allowed to fly at, depending on your direction of flight. Oh, and the equipment that you've got on your aircraft. And the time of day (in some circumstances) And the day of the week(in other circumstances) And the fact that Air traffic control needs to know where you're planning on flying. Europe is even more difficult to fly in based on all of the restrictions that they put against the flight paths attempting to adjust the air traffic flow.
Oh, or were you basing the comment on the tiny non-jets(piston/turboprop) that can't fly very high. (speaking as someone who's attempting to manage this data for commercial flight planning purposes)
I also live in Canada - TiVo isn't _officially_ supported here, although I run my TiVo with local guide listings, current time zone and current listings. I support it using xmltv and assistance from a bunch of people on the Internet, along with a couple of perl/tcl scripts (although some people are using VB for their guide downloads.).
For me I think I spent $300 + shipping + $ for new drives, but that's it, and I've been running it for ~1yr now.
Sadly it doesn't have HDTV, but I haven't been able to determine if any of the HD tuners out there will take component input anyways... (there is no over the air HDTV channels that I know of in my area)
Really I love my TiVo, I couldn't build a comparable machine for a comparable price at the time.
(We don't help any people from TiVo supported countries with getting the service for free, so don't bother asking)
If you're trying to track down memory leaks/overruns/general corruption in C or C++, even in multi-threaded apps, I've found Insure++ from Parasoft extremely helpful.
It even tracks corruption on your stack (something I couldn't find in any other piece of software for x86/Linux)
Slashdot Mirror
I have no problem with Bell slowing down my P2P transfers when there's congestion. However, from experience, Bell throttles based on time and not bandwidth/congestion.
As soon as the throttling times are over, the P2P downloads speed up considerably, so it's obviously not throttled based on congestion on the network.
As for downloading when it's not affecting others. It would only affect you if they were experiencing congestion, not based on time of day; which is what they have implemented.
Bell is artificially slowing down their customers during certain hours of the day because they are unable to implement a correct solution to handle congestion.
wrt airplane fuel:
Actually there are some companies out there that do payload and fuel optimization with knowledge of fuel prices, payload weights, aircraft performance, forecast wind patterns.
There is also a cost in flying with more fuel than you need, as it takes fuel to transport fuel to your destination.
The algorithms for figuring out how much fuel to put on board aren't particularly difficult (at least when I was working on it) it's just _really_ computationally expensive, and also estimations upon estimations, upon estimations, upon predictions.
Another thing to be considered: the way the plane is packed will also adjust the amount of fuel they use. So when you're packing a plane, you've got to deal with weights side to side, and front to back too.
0K is absolute zero;
absolute zero is at -273.15C
so 200K would work out to -73.15C wouldn't it?
I've learned to trust Google; it's normally correct.
Except for all of the regulations on exactly which flight levels you're allowed to fly at, depending on your direction of flight.
Oh, and the equipment that you've got on your aircraft.
And the time of day (in some circumstances)
And the day of the week(in other circumstances)
And the fact that Air traffic control needs to know where you're planning on flying.
Europe is even more difficult to fly in based on all of the restrictions that they put against the flight paths attempting to adjust the air traffic flow.
Oh, or were you basing the comment on the tiny non-jets(piston/turboprop) that can't fly very high.
(speaking as someone who's attempting to manage this data for commercial flight planning purposes)
I also live in Canada - TiVo isn't _officially_ supported here, although I run my TiVo with local guide listings, current time zone and current listings. I support it using xmltv and assistance from a bunch of people on the Internet, along with a couple of perl/tcl scripts (although some people are using VB for their guide downloads.).
For me I think I spent $300 + shipping + $ for new drives, but that's it, and I've been running it for ~1yr now.
Sadly it doesn't have HDTV, but I haven't been able to determine if any of the HD tuners out there will take component input anyways... (there is no over the air HDTV channels that I know of in my area)
Really I love my TiVo, I couldn't build a comparable machine for a comparable price at the time.
(We don't help any people from TiVo supported countries with getting the service for free, so don't bother asking)
If you're trying to track down memory leaks/overruns/general corruption in C or C++, even in multi-threaded apps, I've found Insure++ from Parasoft extremely helpful. It even tracks corruption on your stack (something I couldn't find in any other piece of software for x86/Linux)