If you happen to be looking for something a little different and have an open mind, I'd say it's definitely worth a listen. It is definitely one of the most pleasant nearly-random musical finds of my life. Ben Folds had a pretty big hand in it, so fans of Ben may be more likely to appreciate it than others.
As it is, it's not uncommon for me to be able to pull less than 700Kb/s down on my "up to" 10Mb/s connection, which is, in my opinion, disgraceful. 3Mb/s as a guaranteed minimum would actually be a blessing.
The issue isn't so much that they advertise the [generally unattainable] maximum; it's more that they don't advertise or adhere to any minimum speed or QoS metrics.
defiantly and proudly stupid.
I can't thank you enough for using that word in an appropriate context. That's probably the first time in 6 months I've seen defiantly on the internet and not wanted to murder the person that typed it.
Interestingly enough, as off-topic as I expected this to be, I was surprised at how on-topic it was, given the subject matter.
I managed to reattach the heat sink, and that CPU is still working fine today. If this throttling were not included, I guarantee you that would have been the end of that chip.
My employer has a very large, and, IMO very organized, but incomprehensibly so, codebase. There aren't a lot of high-level specs, and there aren't a lot of good comments in the code. There are a lot of times where I will be tasked with finding a bug, and I can see where the program breaks as well as why it breaks, but without knowing what it's supposed to do, it's hard for me to make the right fix. There are a lot of places where we have some 1500-line (don't even get me started on this) C++ function handling some enormous data structures (20+ member variables, of which roughly half of those are equally-large data structures) and there's basically no info on what any of it is really supposed to do (other than whatever function/variable names there are).
Whenever I'm not cleaning up other peoples' messes, I tend to focus on making sure it's obvious what I was trying to do and that the input/output of my function is well-specified, so if someone comes along behind me it's easier for them to locate the "true" problem by looking at the specifications than just finding a "problem" and trying to make sure it doesn't happen again with some quick fix. I also try to keep my functions as task-specific as possible and small enough to be somewhat comprehensible on their own while considering that we don't have unlimited stack space on our devices.
But, then again, I'm relatively new there. They might break my will eventually...
Ha. Sorry dude. I doubt it's worth your time, and I'm way too lazy to ship it. It was only a $40 card to begin.
I'll figure something out. Use it in another machine or see how it does with Windows 7.
many faults are not temperature related, and will not show up on this test.
I've actually had a lot of well-performing and well-cooled hardware that just doesn't work right. I recently gave up on a video card because it was randomly bringing the entire system to its knees (I suspect the drivers were waiting on a lock or something), and would ultimately lead to a hard crash. If the system was never allowed to sleep, it would be fine with whatever load it was subjected to. Once it had come out of standby, all bets were off as to whether the system would slow, hang, or crash and how long it would take to get there.
Overall it just seems that I hit upon a specific configuration/code path that is probably a driver issue, but definitely not temperature related and just as problematic as a hardware issue if all drivers behave similarly (and hard to use an overclocking tool to test). I replaced it with a (...ok, *the*) different brand of GPU and everything has been working fine since.