Sure. Here we go:

perf stat on first PC (i7-6700K @ 4.00GHz x 8 CPU, 32GiB RAM):

        395,282.24 msec task-clock                       #    5.612 CPUs
utilized
         4,982,318      context-switches                 #   12.604 K/sec

         1,258,234      cpu-migrations                   #    3.183 K/sec

         1,698,192      page-faults                      #    4.296 K/sec

 1,558,005,376,132      cycles                           #    3.942 GHz

 1,085,678,118,192      instructions                     #    0.70  insn
per cycle
   130,242,817,239      branches                         #  329.493 M/sec

     1,513,065,695      branch-misses                    #    1.16% of all
branches

      70.439261508 seconds time elapsed
     351.168298000 seconds user
      44.239862000 seconds sys


perf stat on second PC (i7-10700 @ 2.90GHz x 16 CPU, 64GiB RAM):

        277,595.50 msec task-clock                       #    8.502 CPUs
utilized
         3,356,252      context-switches                 #   12.090 K/sec

           872,020      cpu-migrations                   #    3.141 K/sec

         1,671,597      page-faults                      #    6.022 K/sec

 1,257,017,696,457      cycles                           #    4.528 GHz

   590,118,043,095      instructions                     #    0.47  insn
per cycle
    70,240,995,962      branches                         #  253.034 M/sec

       734,712,605      branch-misses                    #    1.05% of all
branches

      32.651035006 seconds time elapsed
     254.315463000 seconds user
      23.384174000 seconds sys


On Mon, 10 Feb 2025 at 13:26, Simon Sobisch <simonsobi...@gnu.org> wrote:

> Just out of interest: can you run
>
>      perf stat yourprog
>
> (depending on your setup that may need root or a temporary adjustment of
> the paranoid setting) on both machines and share the results - just to
> know what we're actually talking about...
>
> Simon
>
> Am 10.02.2025 um 11:02 schrieb Lev Yudalevich:
> > The program being tested is not single-threaded. In fact, it is
> > "extremely" multi-threaded. That's why I was expecting faster runs.
> >
> > On Mon, 10 Feb 2025 at 11:54, David Faure <fa...@kde.org
> > <mailto:fa...@kde.org>> wrote:
> >
> >     On Monday, 10 February 2025 09:44:39 Lev Yudalevich wrote:
> >      > My first PC has i7-6700K @ 4.00GHz x 8 CPU, 32GiB RAM
> >      > My second PC has i7-10700 @ 2.90GHz x 16 CPU, 64GiB RAM
> >      > Both machines have identical OS installation (Ubuntu 22.04.5 LTS)
> >     rest of
> >      > the software (toolchains etc).
> >      > However, running Valgrind (version 3.25.0.GIT) with the same test
> >     program
> >      > on a second (presumably more powerful) machine is more than twice
> >     slower
> >      > than running the same on the first machine. What can be a reason
> >     for this?
> >      > I'd really appreciate any hint/help/idea. Thank you. Lev.
> >
> >     2.9 GHz < 4.0 GHz so it seems to me the second PC has a slower CPU.
> >     Assuming that the program is single-threaded, this explains why the
> >     second
> >     machine is actually slower.
> >
> >     --
> >     David Faure, fa...@kde.org <mailto:fa...@kde.org>, http://
> >     www.davidfaure.fr <http://www.davidfaure.fr>
> >
> >
> >
> > _______________________________________________
> > Valgrind-users mailing list
> > Valgrind-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/valgrind-users
>
>
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Reply via email to