By: Simon Farnsworth (simon.delete@this.farnz.org.uk), October 31, 2016 4:42 am
Room: Moderated Discussions
juanrga (noemail.delete@this.juanrga.com) on October 31, 2016 4:35 am wrote:
> Travis (travis.downs.delete@this.gmail.com) on October 30, 2016 6:34 pm wrote:
> > juanrga (noemail.delete@this.juanrga.com) on October 29, 2016 9:47 pm wrote:
> > > anon (spam.delete.delete@this.this.spam.com) on October 28, 2016 4:13 am wrote:
> > > > juanrga (noemail.delete@this.juanrga.com) on October 28, 2016 2:02 am wrote:
> > >
> > >
> > >
> >
> > Your claim doesn't make a lot of sense. The point is that frequency and IPC exist two somewhat
> > opposite points in the multi-dimensional tradeoff space used in CPU design - more "brainy"
> > designs may give up frequency to get more IPC.
>
> You are repeating what I said before. I wrote there is inverse relation between
> IPC and frequency, and I wrote that this inverse relation is the basis for
> the traditional definition of speed-demons and brainiac desings.
>
> > The main point made was that you can't simply evaluate in a quantitative way the coefficients in this
> > tradeoff (i.e., how much IPC you gain by reducing f) by taking an existing chip and downclocking it!
> > That will only give a small IPC boost due to decreased relative DRAM latency (and perhaps L3 or L4
> > latency for systems where those caches are in a separate clock domain). The main IPC benefit to reduced
> > frequencies is missed: the ability to use the longer clock cycles to stuff in more logic per pipeline
> > stage, to reduce the number of pipeline stages, to increase cache sizes, whatever.
>
> That wasn't the point.
>
> We are not saying that taking a given F chip and underclocking it to F/2 gives
> a measure of the IPC that would have a chip initially designed for F/2.
>
> This is the second time that my point is ignored.
>
> > Claiming that the same logic works in reverse is nonsensical - you can't just upclock a 2 Ghz design
> > to 4 Ghz, unless the design was terrible and left a lot on the table in the first place...
>
> I didn't write that same logic applies. I said that essentially the same law
> applies to the IPC/F relation, but with different parameters, of course.
>
> I think here the confusion here relies on that I am considering a single law with different parameters,
> whereas some of you are taking the different expressions with different parameters as different laws.
The confusion seems to be that you believe that a chip designed for 2 GHz can be overclocked to 4 GHz at all. This is not a given (unlike underclocking a chip designed for 4 GHz to 2 GHz), and thus the relationship, while trivially true, is also worthless.
Put another way, if I say that the energy cost of cycling at 20 kph is 120 J/km, and the energy cost of driving my car at 80 kph is 2 MJ/km, but the energy cost of driving my car at 20 kph is 3 MJ/km, I can't then say "and if I cycled at 80 kph, I'd therefore only need 80 J/km". Not because the data doesn't support that, but because I can't cycle that fast.
> Travis (travis.downs.delete@this.gmail.com) on October 30, 2016 6:34 pm wrote:
> > juanrga (noemail.delete@this.juanrga.com) on October 29, 2016 9:47 pm wrote:
> > > anon (spam.delete.delete@this.this.spam.com) on October 28, 2016 4:13 am wrote:
> > > > juanrga (noemail.delete@this.juanrga.com) on October 28, 2016 2:02 am wrote:
> > >
> > >
My point is that Apple can target 4GHz for some future chip, miss some few IPC percents
> > > compared to current designs and then recover those percents via hardware improvements.
> > >
> >
> > Your claim doesn't make a lot of sense. The point is that frequency and IPC exist two somewhat
> > opposite points in the multi-dimensional tradeoff space used in CPU design - more "brainy"
> > designs may give up frequency to get more IPC.
>
> You are repeating what I said before. I wrote there is inverse relation between
> IPC and frequency, and I wrote that this inverse relation is the basis for
> the traditional definition of speed-demons and brainiac desings.
>
> > The main point made was that you can't simply evaluate in a quantitative way the coefficients in this
> > tradeoff (i.e., how much IPC you gain by reducing f) by taking an existing chip and downclocking it!
> > That will only give a small IPC boost due to decreased relative DRAM latency (and perhaps L3 or L4
> > latency for systems where those caches are in a separate clock domain). The main IPC benefit to reduced
> > frequencies is missed: the ability to use the longer clock cycles to stuff in more logic per pipeline
> > stage, to reduce the number of pipeline stages, to increase cache sizes, whatever.
>
> That wasn't the point.
>
> We are not saying that taking a given F chip and underclocking it to F/2 gives
> a measure of the IPC that would have a chip initially designed for F/2.
>
> This is the second time that my point is ignored.
>
> > Claiming that the same logic works in reverse is nonsensical - you can't just upclock a 2 Ghz design
> > to 4 Ghz, unless the design was terrible and left a lot on the table in the first place...
>
> I didn't write that same logic applies. I said that essentially the same law
> applies to the IPC/F relation, but with different parameters, of course.
>
> I think here the confusion here relies on that I am considering a single law with different parameters,
> whereas some of you are taking the different expressions with different parameters as different laws.
The confusion seems to be that you believe that a chip designed for 2 GHz can be overclocked to 4 GHz at all. This is not a given (unlike underclocking a chip designed for 4 GHz to 2 GHz), and thus the relationship, while trivially true, is also worthless.
Put another way, if I say that the energy cost of cycling at 20 kph is 120 J/km, and the energy cost of driving my car at 80 kph is 2 MJ/km, but the energy cost of driving my car at 20 kph is 3 MJ/km, I can't then say "and if I cycled at 80 kph, I'd therefore only need 80 J/km". Not because the data doesn't support that, but because I can't cycle that fast.
Topic | Posted By | Date |
---|---|---|
Neat die area comparison image | Rob | 2016/10/21 05:39 PM |
Neat die area comparison image | anonymou5 | 2016/10/21 06:44 PM |
Neat die area comparison image | Mr. Camel | 2016/10/22 04:58 AM |
Neat die area comparison image | Heikki Kultala | 2016/10/22 05:19 AM |
Neat die area comparison image | Mr. Camel | 2016/10/22 07:10 AM |
Neat die area comparison image | Mr. Camel | 2016/10/22 07:15 AM |
different caches... | Heikki Kultala | 2016/10/22 08:29 AM |
Broadwell includes LLC, just for comparision | anon | 2016/10/22 08:52 AM |
Broadwell includes LLC, just for comparision | juanrga | 2016/10/23 06:09 AM |
Broadwell includes LLC, just for comparision | anon | 2016/10/23 07:25 AM |
Broadwell includes LLC, just for comparision | juanrga | 2016/10/25 09:57 AM |
Broadwell includes LLC, just for comparision | Simon Farnsworth | 2016/10/25 11:03 AM |
Broadwell includes LLC, just for comparision | juanrga | 2016/10/28 02:02 AM |
Broadwell includes LLC, just for comparision | anon | 2016/10/28 04:13 AM |
Broadwell includes LLC, just for comparision | juanrga | 2016/10/29 09:47 PM |
Broadwell includes LLC, just for comparision | Travis | 2016/10/30 06:34 PM |
Broadwell includes LLC, just for comparision | juanrga | 2016/10/31 04:35 AM |
Broadwell includes LLC, just for comparision | Simon Farnsworth | 2016/10/31 04:42 AM |
Broadwell includes LLC, just for comparision | anon | 2016/11/01 12:56 PM |
Broadwell includes LLC, just for comparision | Maynard Handley | 2016/11/01 01:37 PM |
Broadwell includes LLC, just for comparision | anon | 2016/11/01 04:22 PM |
Broadwell includes LLC, just for comparision | Maynard Handley | 2016/11/01 07:30 PM |
Broadwell includes LLC, just for comparision | anon | 2016/11/02 06:15 AM |
Broadwell includes LLC, just for comparision | Maynard Handley | 2016/11/02 09:23 AM |
Broadwell includes LLC, just for comparision | anon | 2016/11/02 11:50 AM |
Broadwell includes LLC, just for comparision | Simon Farnsworth | 2016/11/02 02:48 AM |
Broadwell includes LLC, just for comparision | Simon Farnsworth | 2016/10/28 06:19 AM |
Broadwell includes LLC, just for comparision | juanrga | 2016/10/29 10:15 PM |
Broadwell includes LLC, just for comparision | Simon Farnsworth | 2016/10/30 12:31 PM |
Broadwell includes LLC, just for comparision | Ricardo B | 2016/10/29 05:30 PM |
underclocked is different than designed for low clock speed | Heikki Kultala | 2016/10/25 11:47 PM |
underclocked is different than designed for low clock speed | Maynard Handley | 2016/10/26 10:07 AM |
That wasn't the point | juanrga | 2016/10/28 02:15 AM |
Even without the point you have invalid comparison | Heikki Kultala | 2016/10/28 09:03 AM |
8 wide vs 6 wide | juanrga | 2016/10/29 10:41 PM |
8 wide vs 6 wide | Wilco | 2016/10/30 05:00 AM |
8 wide vs 6 wide | Doug S | 2016/10/30 12:20 PM |
8 wide vs 6 wide | Wilco | 2016/10/30 01:12 PM |
8 wide vs 6 wide | juanrga | 2016/10/30 02:56 PM |
8 wide vs 6 wide | Travis | 2016/10/30 07:13 PM |
8 wide vs 6 wide | juanrga | 2016/10/31 04:55 AM |
8 wide vs 6 wide | anon | 2016/11/01 01:00 PM |
SoftMachines | none | 2016/11/02 03:57 AM |
SoftMachines | David Kanter | 2016/11/02 08:53 AM |
8 wide vs 6 wide | juanrga | 2016/11/03 12:35 PM |
8 wide vs 6 wide | Wilco | 2016/11/03 02:13 PM |
8 wide vs 6 wide | juanrga | 2016/11/03 07:35 PM |
8 wide vs 6 wide | Wilco | 2016/11/04 01:27 PM |
8 wide vs 6 wide | juanrga | 2016/11/04 06:08 PM |
8 wide vs 6 wide | Wilco | 2016/11/06 04:52 AM |
8 wide vs 6 wide | juanrga | 2016/11/06 04:56 PM |
8 wide vs 6 wide | Wilco | 2016/11/07 04:25 AM |
8 wide vs 6 wide | Aaron Spink | 2016/11/04 04:08 PM |
8 wide vs 6 wide | juanrga | 2016/11/04 06:10 PM |
Dunning-Krueger effect | Heikki Kultala | 2016/11/04 03:22 AM |
Dunning-Krueger effect | itsmydamnation | 2016/11/04 02:48 PM |
8 wide vs 6 wide | anon | 2016/11/04 03:38 AM |
8 wide vs 6 wide | juanrga | 2016/11/04 05:05 AM |
8 wide vs 6 wide | anon | 2016/11/04 06:12 AM |
8 wide vs 6 wide | Wilco | 2016/11/04 01:12 PM |
8 wide vs 6 wide | anon | 2016/11/04 02:54 PM |
8 wide vs 6 wide | juanrga | 2016/11/04 05:34 PM |
8 wide vs 6 wide | anon | 2016/11/05 02:14 AM |
8 wide vs 6 wide | juanrga | 2016/11/04 05:39 PM |
8 wide vs 6 wide | Wilco | 2016/11/06 05:15 AM |
8 wide vs 6 wide | juanrga | 2016/11/06 05:06 PM |
8 wide vs 6 wide | Wilco | 2016/11/07 03:45 AM |
8 wide vs 6 wide | David Kanter | 2016/11/07 08:43 PM |
8 wide vs 6 wide | Wilco | 2016/11/08 03:57 AM |
8 wide vs 6 wide | juanrga | 2016/11/14 12:12 PM |
8 wide vs 6 wide | Wilco | 2016/11/14 04:53 PM |
8 wide vs 6 wide | dmcq | 2016/11/15 03:17 AM |
8 wide vs 6 wide | Wilco | 2016/11/15 03:43 AM |
8 wide vs 6 wide | dmcq | 2016/11/15 04:28 AM |
1 µop per instruction is not necessary | Paul A. Clayton | 2016/11/17 12:09 PM |
8 wide vs 6 wide | juanrga | 2016/11/20 06:56 AM |
8 wide vs 6 wide | Wilco | 2016/11/21 05:54 PM |
8 wide vs 6 wide | juanrga | 2016/11/22 08:49 AM |
8 wide vs 6 wide | Wilco | 2016/11/22 03:25 PM |
8 wide vs 6 wide | Wilco | 2016/10/31 03:03 AM |
Skylake can retire 8 uops | David Kanter | 2016/10/31 12:41 AM |
Skylake can retire 8 uops | juanrga | 2016/10/31 04:15 AM |
Skylake can retire 8 uops | Alberto | 2016/11/04 07:22 AM |
8 wide vs 6 wide bogus numbers | Heikki Kultala | 2016/10/30 06:25 AM |
Broadwell includes LLC, just for comparision | anon | 2016/10/26 03:10 AM |
Pushing the hidden agenda | juanrga | 2016/10/28 03:11 AM |
Pushing the hidden agenda | anon | 2016/10/28 04:35 AM |
Neat die area comparison image | David Hess | 2016/10/22 01:26 PM |
Neat die area comparison image | anon2 | 2016/10/22 05:20 PM |
Neat die area comparison image | David Hess | 2016/10/22 10:31 PM |
Neat die area comparison image | anon2 | 2016/10/23 01:50 AM |
Neat die area comparison image | Travis | 2016/10/24 01:26 PM |
Neat die area comparison image | Maynard Handley | 2016/10/24 04:27 PM |
Neat die area comparison image | juanrga | 2016/10/25 10:02 AM |
Neat die area comparison image | David Hess | 2016/10/25 09:59 PM |
Neat die area comparison image | Travis | 2016/10/25 10:22 PM |
Neat die area comparison image | David Hess | 2016/10/25 10:37 PM |
Neat die area comparison image | Travis | 2016/10/30 06:09 PM |
Neat die area comparison image | Gabriele Svelto | 2016/10/26 02:23 AM |
Neat die area comparison image | Doug S | 2016/10/26 08:17 AM |
Neat die area comparison image | Jukka Larja | 2016/10/27 09:28 AM |
Neat die area comparison image | anon | 2016/10/26 03:32 AM |
Neat die area comparison image | juanrga | 2016/10/23 06:29 AM |
Neat die area comparison image | Matthias Waldhauer | 2016/10/22 06:12 AM |
Neat die area comparison image | juanrga | 2016/10/23 05:44 AM |
Neat die area comparison image | Gabriele Svelto | 2016/10/24 02:17 AM |