Rumored Specs & Details of Intels Upcoming KabyLake Lineup

[Tech_Dreamer]

Hmm..This lake water tastes a bit salty,

 

So many Sevens!

 

Nothing much to say & nothing unexpected , Like every other previous years Line up , Sources are shady , WCCF to begin with this is their sources sites  graphic showing the specs , Pretty much it's believable & we get a glimpse of the product models , Not sure if there would be dual core i3 variants of these, Prices as you can expect might be up a bit , since it's boasting 10% improvement over the current gen in a news i read earlier..so post your thoughts & itty bitty things down there at the comment section

 

 

i7-7777 007 (Looks like Grits & gravy rolled out their names #RollAnotherDice)

 

Additional Rumors :

• Desktop CPU are rumored a year away,Laptop's will be integrating this one first
• Kaby Lake will add native USB 3.1 Generation 2 Ports
• 10% IPC improvement

 

Not sure if AMD will offer any competition but read about that here >>

 

 

 

 

Source:

http://www.coolaler.com/content.php/6761

http://wccftech.com/intel-kaby-lake-desktop-lineup-leak/

 

 

 

 

 

 

[xentric]

Krabby Lake

[migeo]

Just now, xentric said:

Krabby Lake

lel

[Tech_Dreamer]

1 minute ago, xentric said:

Krabby Lake

 

[AresKrieger]

2 minutes ago, xentric said:

Krabby Lake

I wish it was called that, dafuq is a kaby, the only thing I can think of is the slang term for cab driver but that is a c not a k

[Castdeath97]

6 minutes ago, AresKrieger said:

I wish it was called that, dafuq is a kaby, the only thing I can think of is the slang term for cab driver but that is a c not a k

It's the creature that lives under the ivy bridge that goes over the sky lake.

[Senzelian]

12 hours ago, AresKrieger said:

I wish it was called that, dafuq is a kaby, the only thing I can think of is the slang term for cab driver but that is a c not a k

Kaby is just a name.

The Kaby Lake is literally a real lake in Ontario. 

[ScratchCat]

A small IPC leap for Intel but a GIANT IPC step for AMDkind

[Bananasplit_00]

15 minutes ago, Senzelian said:

Kaby is just a name.

The Kaby Lake is literally a real lake in Ontario. 

so is the sky lake a thing too? and the Ivy brdge?  

[patrickjp93]

1 hour ago, Bananasplit_00 said:

so is the sky lake a thing too? and the Ivy brdge?  

Yes. Intel names all of its architectures after real geographical locations.

[TidaLWaveZ]

lol grits n' gravy

[Bananasplit_00]

3 hours ago, patrickjp93 said:

Yes. Intel names all of its architectures after real geographical locations.

so where is the sky lake then? id love to know

[Trixanity]

1 hour ago, Bananasplit_00 said:

so where is the sky lake then? id love to know

https://en.wikipedia.org/wiki/Sky_Lake,_Florida I guess. The only thing I could find.

[Coaxialgamer]

Wow , that's a great core colck on that i7

[patrickjp93]

3 hours ago, Bananasplit_00 said:

so where is the sky lake then? id love to know

 

2 hours ago, Trixanity said:

https://en.wikipedia.org/wiki/Sky_Lake,_Florida I guess. The only thing I could find.

There is one in France as well.

[Agosto]

I thought Kaby Lake was just a Skylake refresh... 10% IPC improvement? That's a bigger jump than Hawell to Skylake...

[Tech_Dreamer]

8 hours ago, ScratchCat said:

A small IPC leap for Intel but a GIANT IPC step for AMDkind

Probably fake just like the moon landing *grabs space popcorn*

13 minutes ago, Agost said:

I thought Kaby Lake was just a Skylake refresh... 10% IPC improvement? That's a bigger jump than Hawell to Skylake...

Rumor

[MageTank]

21 hours ago, Tech_Dreamer said:

 

 

Additional Rumors :

• 10% IPC improvement

I genuinely hope nobody believes this. They are going to be in for a bad time. 

[That Norwegian Guy]

"Let's make architectural spin-offs whose only improvement is the iGPU"

"Oh yeah, let's cut out i3 and Pentium from that line up since nobody could POSSIBLY want pairings of lower-tier CPUs with not-as-sucky-as-usual iGPUs. RIGHT?!?!?"

 

More garbage from the muppets at Intel.

 

Priced out of HTPC realm, no niche in the performance realm.

[NumLock21]

The interesting cpus will be SKL-X and KBL-X

SKL-E is successor to BW-E, those X is something in between.

[themctipers]

who fucking cares

bit more ipc, maybe lower thermals, bam new generation. 

 

if intel has a mainstream 6 core one, and maybe 12mb cache sure. 

[patrickjp93]

51 minutes ago, themctipers said:

who fucking cares

bit more ipc, maybe lower thermals, bam new generation. 

 

if intel has a mainstream 6 core one, and maybe 12mb cache sure. 

No point. Until mainstream software actually starts scaling well with that many cores, there's just no point to kneecap future sales by giving them away now.

[themctipers]

Just now, patrickjp93 said:

No point. Until mainstream software actually starts scaling well with that many cores, there's just no point to kneecap future sales by giving them away now.

so far, you're correct. most of the software I use is single threaded but chrome is multithreaded. and chrome eats up most of my cpu time.  

tumblr takes alot of cpu time for me  

[patrickjp93]

4 minutes ago, themctipers said:

so far, you're correct. most of the software I use is single threaded but chrome is multithreaded. and chrome eats up most of my cpu time.  

tumblr takes alot of cpu time for me  

Most of that is just the CPU cores polling the NICs to see if packets have arrived. Chrome doesn't utilize any waiting/backoff techniques. It only LOOKS like it's stressing your CPU.

 

If you launch 4 threads with the following code on a quad-core machine, you'll get 100% CPU utilization.

 

 

void dummyfunc() {

    while(true){}

}

 

int main() {

    for(uint i = 0; i < 4; ++i) {

        std::thread(dummyfunc);

    }

}

[themctipers]

Just now, patrickjp93 said:

Most of that is just the CPU cores polling the NICs to see if packets have arrived. Chrome doesn't utilize any waiting/backoff techniques. It only LOOKS like it's stressing your CPU.

 

If you launch 4 threads with the following code, you'll get 100% CPU utilization.

 

 

void dummyfunc() {

    while(true){}

}

 

int main() {

    for(uint i = 0; i < 4; ++i) {

        std::thread(dummyfunc);

    }

}

 close enough.