From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15832] Low performance with python3 compare to python2 on the same platform
Date: Fri, 27 Oct 2023 17:27:29 +0000 [thread overview]
Message-ID: <bug-15832-163-byGUFJEvFI@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 #1 from Vincent Fazio <vfazio@xes-inc.com> ---
What's the output of `python -m cProfile test_python.py 10000000` on each?
I do see some variances even in Docker containers but not to that degree. On an
rpi CM3 it doesn't take anywhere near the numbers you're posting below (only
8s).
One option would be to profile the python interpreter itself. 3.12 has hooks
for `perf` but they may not be representative of the situation you're seeing as
recent interpreters try to perform opcode specialization. Otherwise you may
have to build the interpreter with profiling enabled and use another external
tool to collect that data.
--
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
next parent reply other threads:[~2023-10-27 17:27 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 ` bugzilla [this message]
2023-11-02 15:05 ` [Buildroot] [Bug 15832] Low performance with python3 compare to python2 on the same platform bugzilla
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-byGUFJEvFI@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