By: Travis Downs (travis.downs.delete@this.gmail.com), August 17, 2018 8:16 am
Room: Moderated Discussions
Adrian (a.delete@this.acm.org) on August 16, 2018 11:31 pm wrote:
> Travis (travis.downs.delete@this.gmail.com) on August 15, 2018 12:52 pm wrote:
> >
> > Is anyone aware of any out-of-the box thing to either measure this or read the frequency
> > from MSRs (I forget if these modes are both exposed, I think so though).
> >
>
>
> On Linux it is very easy to measure everything you want to know with turbostat.
>
> This program should be available as a package in whatever distribution you
> use, but it is preferable to use the most recent version, which you can make
> and install yourself from the Linux kernel sources, typically located at:
>
> /usr/src/linux/tools/power/x86/turbostat/
>
>
> Turbostat can show the clock frequencies of each core and all the other relevant information.
>
>
> You should run simultaneously with turbostat some program which completely loads the processor
> on the desired number of cores, e.g. firestarter or some AVX-512 / AVX2 benchmark.
>
Yup, although I was actually asking if turbostar or some other program could measure the nominal/configured AVX frequencies, regardless of what is running (of if nothing is running). It can do so at least for the non-AVX frequencies if you pass --debug (and recent versions show this info without debug also).
> Travis (travis.downs.delete@this.gmail.com) on August 15, 2018 12:52 pm wrote:
> >
> > Is anyone aware of any out-of-the box thing to either measure this or read the frequency
> > from MSRs (I forget if these modes are both exposed, I think so though).
> >
>
>
> On Linux it is very easy to measure everything you want to know with turbostat.
>
> This program should be available as a package in whatever distribution you
> use, but it is preferable to use the most recent version, which you can make
> and install yourself from the Linux kernel sources, typically located at:
>
> /usr/src/linux/tools/power/x86/turbostat/
>
>
> Turbostat can show the clock frequencies of each core and all the other relevant information.
>
>
> You should run simultaneously with turbostat some program which completely loads the processor
> on the desired number of cores, e.g. firestarter or some AVX-512 / AVX2 benchmark.
>
Yup, although I was actually asking if turbostar or some other program could measure the nominal/configured AVX frequencies, regardless of what is running (of if nothing is running). It can do so at least for the non-AVX frequencies if you pass --debug (and recent versions show this info without debug also).
Topic | Posted By | Date |
---|---|---|
AVX2 and AVX-512 frequencies for W-2014 | Travis | 2018/08/14 08:37 PM |
Should say W-2104 (NT) | Travis | 2018/08/14 08:50 PM |
AVX2 and AVX-512 frequencies for W-2014 | Adrian | 2018/08/15 12:17 AM |
AVX2 and AVX-512 frequencies for W-2014 | Travis | 2018/08/15 12:52 PM |
AVX2 and AVX-512 frequencies for W-2014 | Jeff S. | 2018/08/16 06:19 AM |
AVX2 and AVX-512 frequencies for W-2014 | Travis | 2018/08/16 09:09 AM |
AVX2 and AVX-512 frequencies for W-2014 | Travis | 2018/08/23 11:25 PM |
AVX2 and AVX-512 frequencies for W-2014 | Adrian | 2018/08/16 11:31 PM |
AVX2 and AVX-512 frequencies for W-2014 | Travis Downs | 2018/08/17 08:16 AM |
AVX2 and AVX-512 frequencies for W-2014 | Adrian | 2018/08/17 10:29 AM |
AVX2 and AVX-512 frequencies for W-2014 | Travis | 2018/08/19 11:40 AM |
AVX2 and AVX-512 frequencies for W-2104 | Travis | 2018/08/23 10:49 PM |
AVX2 and AVX-512 frequencies for W-2104 | Adrian | 2018/08/24 02:32 AM |