Lol what
Jesus Fucking Christ
>>54833377
How does that even happen?
does the bios/uefi code needs updating?
THIS IS ALL AMD'S FAULT
>underperforming
>overly expensive(bottom SKUs are gimped)
>hot
>can't overclock for shit
These are the worst Xeon scraps Intel has ever made.
>>54833388
Looks like I'll be keeping the 6700K that's in the mail, since it OC's pretty well. Also because my 3570K + Asus mobo combo is pretty much fried (Can't OC 1Mhz, can't shut down, only reboot).
>>54833599
Obvious mobo problem.
Broadwell-E is fucking disgusting, thanks pajeets
Also there's already a discussion about it
>>54832244
Those benchmarks are fake. Jesus Christ you people gobble up anything by anti Intel media.
>>54833740
>anandtech
>not Nvidiashills
AHAHAHAHAHA kill yourself.
>>54833740
No they're not you fucking retard. Nice try for damage control though.
>>54833740
http://www.anandtech.com/show/10337/the-intel-broadwell-e-review-core-i7-6950x-6900k-6850k-and-6800k-tested-up-to-10-cores/9
>>54833740
> So certain intel can't do wrong.
> Totally blinded by fanboism, inadvertent damage control
Bahahhahhahahah
>>54833755
>>54833761
>>54833788
>>54833807
Fuck off AMD shills.
I'm laughing at your subpar CPUs
Just look at this clusterfuck
>>54833924
>speculation
Also nothing wrong with that frontend, looks like any ol' regular SMT design, including Intels
>>54833935
Intel uses Hyperthreading, not garbage SMT
>>54833377
>tfw 306$ 4790K @3.5Ghz master race
>>54833948
>>54833599
Please report in if you notice any significant performance improvements.
I've been thinking about upgrading my 3570K as well, but it doesn't seem to be worth it spending 600€ for a 10% upgrade.
Maybe it'll make encoding videos a bit faster.
>>54833948
Hey dumbass, Hyperthreading IS SMT, just with a different name.
>>54833977
Why do you respond to that fool?
>>54833377
But what about Cinebench?
If you are going to benchmark 8~10 core CPUs you don't do it with games. Specially when their clock speeds are lower.
![blender_w_600[1].png](https://i.imgur.com/UEuKExE.png "blender_w_600[1].png")
>gaming benchamrks
wow you amdfaggots feel so desperate you go on a hunt for THAT ONE BENCHMARK which is also a fucking gaming benchmark. Show me some proper desktop workforce tests you absolute retards.
>>54833377
DELETE THIS
>>54834020
Since when did you Intelfags care about multi-threaded performance?
>>54833956
>outdated DDR3 ram
>meanwhile DDR4 are going above 4000Mhz for muh FPS.
Is the IHS soldered or does it have the same shitty TIM as all other Intels?
![81824[1].png](https://i.imgur.com/AfGXudV.png "81824[1].png")
>>54833956
Feels fucking good man
>Don't you mean 4.5?
Or is 3.5 some secret clock
>>54834045
It's using solder, they're the HEDT line but they lowered the packaging z height so it can bend easier-
![81818[1].png](https://i.imgur.com/ioNUzHq.png "81818[1].png")
>>54834037
since my rig was making me money by doing actual job like rendering
>>54834067
Ah, so you're the 1%
>>54834074
suits me ;^)
So 5820k>6800k
>>54834079
Well, at least someone's making use of them.
reminder intel hasn't made a good cpu since sandybridge
Got the i7-5930K
Love it.
ZEN ALREADY WON
>>54834120
stop using my internet grandpa
>>54834120
>what is the 4790K
>>54834209
Sandybridge +12% IPC with less overclocking potential
Ergo nothing of value.
>>54834037
Since Core 2 Quad.
>>54834041
Show me worth real life differences in performance with DDR3 vs DDR4, pal.
>>54834057
It was 4.5Ghz typo edition.
>>54834209
>incremental upgrade with a dogshit heatspreader and gimped overclocking
>>54833956
>zero results for reverse image search
Who is this? What is this gif from?
>>54834209
A poorfag chip for those who couldn't afford a i7-5820K/5930K.
>>54834258
Nvm I guess the search just malfunctioned the first time.
>>54834120
e8400 here, can you tell me whats so special about it?
my PC was a beast up to 2011ish and even then it lacks ram.
im asking because im clueless.
>>54834375
Sandy was amazing performance with low heat and high overclocking. Overall was amazing. Since Sandy intel CPU have only been small incremental upgrades per generation. Nothing more than 5-10% tops and nothing worth spending another 400USD on. People with 2500k still play everything pretty damn maxed.
Why should I not just spend the equivalent on a 16 core Xeon if I'm not too interested in gaming perf? I know that the mobos are more expensive, but the 6950X is so fucking shit.
>>54834402
but e8400 isnt a sandy bridge?
>>54834431
E8400 is 45nm C2D.
What irritates me though was that during that time region before Nehalem hit, Intel had cooked up Dunnington, which was in fact 3 pairs of C2D cores and a nice fat lump of L3 cache all on the same die (instead of C2Q's 2x2 configuration), and only released it for Socket 604.
>>54833377
The toys are at it agaim
>>54834457
i feel like a baby listening to an adult. il probably have to google half of what you said.
lurking /g/ for info should be strictly lurking..
cheers.
>>54834067
>Rendering
>On a single CPU
clearly, not enough money.
>>54834492
The E8400 is the second generation of Core 2 Duo, built on the 45nm process node, whereas the first generation was built on the older 65nm process node.
Nehalem is the architecture used for the first generation Core i-series of chips, best known for its use in the i7-920 and its siblings.
Dunnington was Intel's first true "big die" x86 server CPU, and was constructed by throwing on 3 pairs of Core 2 Duo cores, and 8MB of L3 cache to let the 6 cores talk to each other without leaving the die, onto a single die.
Core 2 Quads, both the first and second generation, operated in a 2x Dual-core on the same package configuration, instead of a monolithic quad core die like what AMD did with the first generation Phenoms (which had flaws unfortunately).
Socket 604 was the second, superior variant to the older Socket 603, both of which are server sockets. Socket 604 was used by all of Intel's Core 2 based chips, and could come in configurations of 1 to 4 sockets per machine. It's successor socket was LGA 1366, which was used for first generation i7s and their Xeon equivalents.
>>54834120
phenom II processors was bretty gud for its time
(spoken like a true and ongoing 955 user)
>>54834120
>3400+
>Not the superior 3700+ San Diego with more cache
KEK.
10 core processor for 1700... Presumably meant for professionals. But if you need a lot of threads, you can get an 18 core Xeon for a third the price. You could get two 18 core Xeons and a dual socket mobo for 36 cores.... For less.
Who actually buys this garbage?
>>54833377
4790k owner here
I don't need to say anything at all
>>54833377
So, is it because AMD's GPU code isn't as optimized/parallelized as nvidia's so it wants higher frequencies and less cores? Otherwise, I don't get why they only perform worse with the AMD gpu.
>>54833377
whats with this i7 inconsistency in vidya? how come there is always an i5 that btfo a better i7 processor?
>>54834045
TIM wasn't the problem. It was spacing caused by the glue. TIM was actually good.
>>54834020
Wasn't intel best for gaming because it also happened to be the best processor for other uses?
>>54833377
the 5820k being so far ahead of all the other ones makes no sense. i guess the benchmark isn't really static. meaning, everytime it runs the cars drive differently.
>>54834886
>3700+
>not the superior opteron 144 for half the price and huge OC potential
If I'm going to sli two cards, one is windforce, and the other is evga, the windforce is the stronger fan, so would I have that card on the bottom or the top?
And tell me if I'm stupid for thinking this but I also have a dh15 CPU cooler currently pulling in air from the front of the case. If I wanted to prioritize keeping my cards cool, should I aim it to pull air from the gpu? It's overclocked right now but I'll just be playing vidya so i never really do anything too CPU intensive, if it gets too warm I'll just reduce the OC
>TLDR
If CPU heat is OK can I aim my CPU cooler to pull air from my gpu to keep them cooler?
>>54833948
>>54835484
Fuck I thought it was in sqt
My bad
>>54833377
6950X is a fucking Xeon "reject" that is designed for real world workloads not silly "GAYMING" bullshit.
>>54833388
In all fairness, the auto BIOS over-clocking options are shit.
>>54836071
Even manually it can barely hit 4.0 without bursting into flames
>>54833377
finished and bankrupt
>>54833377
>>54833388
wow great job Intel lol
so glad I just got a 6600K months ago. 4.5 GHz is more than enough
>>54833439
Intel Extreme Shit Edition TM
>>54834002
nobody plays cinebench
games are what most people are going to care about.
>>54834054
>>54834054
So it does make a difference in multi threaded stuff
Hey so now Intel is just like AMD they have 6+ core chips that suck for anything but multi threaded usage.
except AMD's costs $150 and Intel's is $1600
but other than that, yeah. no big deal.
>>54834067
>i speak good english
>i tell truth on /g/
>it not lie why would caveman lie to you on electric message board
>>54834080
uh no, look at the chart right above your post Einstein.
>>54834164
why does Intel all of a sudden think anyone needs more than 4 cores even with hyper threading?
no game or program other than handbrake and cinebench is multi-threaded well enough to use those cores. It's total overkill for the average user or gamer.
>>54833377
88w performing better than 90+ cpus
holy house fire batman
>>54834226
some people need that extra performance
my 6600K is exactly what I needed
>>54834271
her sister is hotter
>>54834623
You don't happen to know all this because of gaming, do you? Please tell me you don't
>>54835002
i5 and i7 are the same thing, i7 just has hyper threading enabled. for an extra $100 this provides a very small benefit if any for games. Games only use 4 cores.
>>54836692
>electric message board
>be vulnerable to viruses
>not using superior rock based message board
>not leaving funny memes on local town boulder
>not being able to shitpost without electric communication
>ever
>>54836719
Intel pushed IPC as hard as they could while AMD pursued threading. Threaded workloads never really caught on in the consumer space, so AMD made Mantle to force the market to get its shit in order. Now Mantle, with proper multithreaded support, is at the core of DX12 and Vulkan and Intel has to release processors that will have to compete with AMD in workloads that AMD has optimized for. One core turbo isn't going to cut it anymore for Intel.
>>54834120
>he doesn't know about the 5820K
>>54833610
Don't know man. It happened to an MSI mobo before the Asus one as well. Then the MSI mobo fried or some shit, so I got the Asus. Wasn't even OC'ing that much on the 3570K. Was like 4.5Ghz or some shit on 1.4V or something.
>>54833958
Well for my current setup which is a 3570K at stock clocks, any OC'ing on the 6700K should be a decent upgrade. If you have OC'ed your 3570K, then I really doubt there would be much difference. I'm really only upgrading because my shit doesn't work properly anymore.
>>54833377
why is the 5820k performing so well? is it the sleeper GOAT high end i7 cpu?
