He also said Sandy Bridge, and 2x2.4, P4 based ones are single core.
The above is a Sandy Bridge Celeron at 2.4 GHz, dual-core. It's closer to his CPU description...
It cannot be Sandy Bridge - SB uses integrated RAM controller which only works with DDR3, yours is DDR1. And Sis651 chipset is for P4 and old Celerons, not Sandy Bridge. Your stuff doesn't add up...
I'm guessing it's an old P4 based Celeron.
Jesus, the article is less than 3 years old. That was the first thing I found when googling "failure rates graphics cards". If you're gonna say "X is better than Y", then maybe it should include the last couple years at least, and not a single series from two particular manufacturers.
If Mercedes S had lower failure rates than BMW X5 in Spain in 2011, does that mean that statistically Mercedes cars have lower failure rates than BMW, and citing a result from 2009 is like comparing cars from the 80's?
You can't make an unqualified 'nVidia is statistically better than AMD' statement and then only accept one cherry-picked recent result. And it's only 3 years old, not 15, many people still have these. You replied to a guy who had 5870, from below, it was actually more reliable than gtx 285, so you're already generalizing to 5000 series yourself.
Only the 69xx of the 6000 series is less reliable, and more like 2x, not 3x. Probably due to the fact that 580 was a refinement of Fermi, and 69xx was a larger architectural change.
And you still haven't cited your source.
I thought that the max OC would be +4 bins, so for 2310 that would be 3.3 GHz, and with turbo you could reach 3.6GHz for one core. Disabling turbo shouldn't affect this limit. This seems like a "faulty" MB implementation or something.
Given that most 2500K reach 4.4+ easily, I've no doubt that the vast majority of 2310s will work fine at 3.8 GHz if one can set it.
Talk about 3 times more failures...
You can see that it varies by manufacturer too, maybe evga is just better than sapphire. And you didn't cite source either.
You do have examples, you just find them on lfsworld like I did:
- for top 3 you have to find drivers in top 10 that have 3 or more people from their country in front of them. T. Stiborek was one such example. If CZE doesn't get points from him, then it's only top 3, if he does, then it's everybody.
- You asked if 11th placed guy should get the points for nutter rank if some points aren't given due to many drivers from the same country. You can check that by finding one example on lfsworld such as Avanah. There are a bunch of Finns in front of him and he's 11th, so you just see in nutter rank if USA got any points from him (he only has that lap, sometimes you need to check that he didn't get points for other combos and sum them up).
All the examples are on lfsworld, so how can you have no examples if you have internet access
No, the extra point goes to no one, and it applies equally to all ranks.
You should try to find an example on LFSW to confirm or disprove your guess, instead of having me look for it every time, next time you're on your own
On BL1/FBM Anavah from US is 11th, and US gets no points from him in the nutter rank.
OK, I've found one
Tomas Stiborek from Czech Rep. He's 4th on Fe3/FXO (7pts) and 10th on Bl1R/FXO (1 pts) so that should be 8 in total. However in nutter rank he contributes 7pts to CZE because on Bl1R/FXO there are 3 other Czech guys faster than him, so he doesn't count
I'm pretty sure it applies to all ranks, nutter rank included. You can try finding an example to prove one way or another. It might be tricky since you need to find someone who doesn't contribute much to nutter rank (so you can check easily), and there's a combo where he's in top 10 and there are 3 people better than him from his country.
If you think you can squeeze in 2500K, then do it, it's better than anything AMD has. Given that you're on budget, 2600K is not worth the price premium.
If not, then AMD. Bulldozer 61xx might be doing well on your particular apps of interests, because it has its strengths, so you may want to check it out. Overall some quad or even hex Phenom 2 is probably a better bang for the money.
I've never heard of any studies showing CPU reliability problems with either company, but it's your call. It reminds me of people who will only buy Japanese or German or American cars because that was their first car and it worked well...
You can see here that nVidia has issues with CS4 as well, in fact there are more nVidia cards there in the list of cards with problems. They are all older, I'm pretty sure that anything new from either nVidia or AMD won't have problems. In any case, I don't see any evidence for this "Adobe and AMD don't work together" view. That site is from Adobe, not like it's some fanboy site.
I don't think you understand what I said, try reading it again.
If you don't believe it then here's a simple test: KY Oval/LX4 is one of the MHR combos. juunasd is 7th, so that means 4pts for Finland, right? Now go to the MHR and click on Finland and look at the responsible racers list - juunasd is not on the list. Notice that 5th placed Alonso[FIN] does appear on the list with 6pts and this is the only MHR combo he drove.
The reason is what I said - there are 3 Finnish guys faster than juunasd on KY1/LX4 so they only get 8+7+6=21 pts there.
Besides I'm telling you something Victor himself said long time ago, it's not like I accidentally noticed this...
There are many changes that are not so visible that were done on Vista/Win7, different driver model, kernel was redesigned for more security etc. Win 7 is simply a better OS. Not that there's anything wrong about using XP, but you'll have to get used to developers not always supporting old OS-es for everything. Like eyefinity.
Lack of indexed file system - I thought NTFS was indexed? If you mean that Windows' search through files is horrible, I agree. I installed cygwin so I could use grep and locate.
It isn't even so bad per se - it's the fact that they worked 3-4 years to deliver something that can't consistently beat even their own CPUs not to mention Sandy Bridge, that makes it quite disappointing.
Obviously they went for the server market, hope they can deliver there. GPUs are also going for the pro market with GCN, but consumers should get a decent performance bump too, I had hoped for the same from Bulldozer, eh...
First, 1600MHz isn't 1600 cycles per second, it's 1,600,000 :P
This is not what CL means, you cannot compute bandwidth (reads/writes per second) in such a naive way:
1600 MHz = 0.625ns per cycle
The time to read amount of memory whose address is known @ CL9:
1 word = 9*0.625ns = 5.625ns (effectively 177M reads/s)
4 words = 9*0.625ns + 3*0.625ns = 7.5ns (effectively 533M reads/s)
16 words = 9*0.625ns + 15*0.625ns = 15ns (effectively 1067M reads/s)
Even though it should be slower by your logic, 1600@CL9 will generally be faster over 800@CL4, because you often read more than just one chunk.
Memory is very slow compared to CPU, so modern CPUs use various mechanisms to avoid memory bottlenecks like L1/L2/L3 caches, out-of-order execution, Intel HT also helps etc. So in real life faster memory won't matter so much in most cases. But there are such cases: take Llano APU, it's graphics part scales very well when you go from 1066MHz to 1866MHz RAM even if higher CL makes this CAS latency about the same, because it cares a lot more about mem bandwidth than CL.
CL factor determines CAS latency and this latency is the same, but that doesn't make CL10@1600 memory no faster than CL5@800. If you're reading more data, or know where it is long enough in advance, the bandwidth will depend more on speed than CL. Say you need to read 4 words/pages of memory (or whatever is the unit), the first one will take the same time, but the next 3 will come 2x quicker for 1600MHz.
As for OP, the build looks ok. 8Gb would be nice since it's cheap, but if it's for gaming, it won't matter as much since most games are 32-bit, thus limited to 2GB of RAM.
The original theme seems settled, and Scawen explicitly asked about button clutch issue. So why exactly is here and now not the right place/time to provide an opinion about it?
You're talking about manually pressing a button. I can concur to some level that it's ok. But using a 3rd party program to create and tweak macros coupled with LFS settings so that you can shift faster than not just AC, but any human with manually using BC, is where the line is crossed IMO. And there's no additional effort with macros, you drive in the exact same way as with AC.
Great. Because I've done it a couple times...
It should still be fixed from LFS. It used to be that you could drive through barriers on BL GP as well as through pits, and easily cut ~1s off your lap. I could use the same argument that it was open to everyone, but it was still fixed because it just isn't right. Maybe this will too if we complain enough :P
I'm late for the original topic (I'm fine with the proposed solution for the tyre preheating anyway), but I can chime in for the button-clutch problem. Yes, it's a pretty big issue and has ruined HL for me to a large degree. As arco said, physics hasn't been reset for a while so most WRs have become quite non-trivial to beat, and it's very sad to see some alien-like WRs being beaten by BC exploits. Majority of WRs in the last 6-12 months have been with BC. It's not a priority, but I'd really like to see something being done about it by the next time the hotlaps on LFSW are reset, as right now I have zero motivation of putting any sort of significant effort into a lap just to see it beaten with BC.
It's not just BC either, seems like the "root of all evil" is the fact that there are faster ways to shift than AC. Even with clutch pedal + shifter I've heard people are using crazy stuff like setting profiler so they need only press the clutch like 25% and using a button to switch between CL+SH and AC so for downshifting when it doesn't matter they just use AC etc. And you can trick LFSW too, there are BC laps on LFSW that are marked AC, so you can't trust that either any more...
On tracks like Bl GP with GTI/TBO, it's an easy 0.2-0.3s. Let's say I drove XRT on some hypothetical track for a year, 8 hours every day, and ended up with a PB of 2.00.00 (assuming a fixed set, i.e. no set-related laptime improvements) . The progress over the year would be roughly:
<2.01.00 - probably in the first couple of laps since it's XRT, my favourite car since S1 demo
~2.00.50 - 1-2 days
~2.00.30 - probably less than a week
The rest of the year would be spent on the remaining 0.3s which would likely be more luck than skill.
On a 2min track, 0.3s is a good estimate for the BC advantage over AC, so if people can't see where the problem lies if someone is given a free 0.3s advantage, then they're not hotlappers IMHO.
No, it won't make an average joe crushing WRs, nor do I care if average people use it. It's fast people who can make a decent lap into something that will make aliens sweat that I care about.