Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15832] Low performance with python3 compare to python2 on the same platform
Date: Thu, 02 Nov 2023 15:05:11 +0000	[thread overview]
Message-ID: <bug-15832-163-MpTTJo32Xa@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15832-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=15832

--- Comment #2 from fabien.nogue@etictelecom.com ---
(In reply to Vincent Fazio from comment #1)

Thank you for your reply.
Here are the outputs of our test with the `cProfile` module:

```
# python2 -m cProfile test_python.py 10000000
         2 function calls in 18.871 seconds

   Ordered by: standard name

   ncalls  tottime  percall  cumtime  percall filename:lineno(function)
        1   18.871   18.871   18.871   18.871 test_python.py:3(<module>)
        1    0.000    0.000    0.000    0.000 {method 'disable' of
'_lsprof.Profiler' objects}


# python3 -m cProfile test_python.py 10000000
         3 function calls in 53.225 seconds

   Ordered by: standard name

   ncalls  tottime  percall  cumtime  percall filename:lineno(function)
        1   53.224   53.224   53.224   53.224 test_python.py:3(<module>)
        1    0.000    0.000   53.225   53.225 {built-in method builtins.exec}
        1    0.000    0.000    0.000    0.000 {method 'disable' of
'_lsprof.Profiler' objects}
```

Is the line `built-in method builtins.exec` relevant?

On the other hand, I am attempting to profile the `cpython` interpreter.
I recompiled `python3` with options `--enable-optimizations` and
`--enable-profiling`, run my test and got the `gmon.out`.
I have `no time accumulated` when I run `gprof` on the output. So far I have no
idea why the profiling output has no result. I need to investigate further.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2023-11-02 15:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-15832-163@https.bugs.busybox.net/>
2023-10-27 17:27 ` [Buildroot] [Bug 15832] Low performance with python3 compare to python2 on the same platform bugzilla
2023-11-02 15:05 ` bugzilla [this message]
2024-06-15 15:13 ` bugzilla

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-15832-163-MpTTJo32Xa@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox