Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Yichun Zhang (agentzh)" <agentzh@gmail.com>
To: gdb-patches <gdb-patches@sourceware.org>
Cc: "Yichun Zhang (agentzh)" <agentzh@gmail.com>
Subject: [PATCH] [python] Optimize python_string_to_host_string() for Python 2.
Date: Wed, 14 Jan 2015 06:38:00 -0000	[thread overview]
Message-ID: <1421217481-18204-1-git-send-email-agentzh@gmail.com> (raw)

Hi,

I have been writing quite some advanced GDB Python tools for LuaJIT
and NGINX in the nginx-gdb-utils project [1] and have been suffering
from serious performance issues even for relatively small working sets.

I have noticed from a typical on-CPU C-land Flame Graph [2]
for my tools that python_string_to_host_string() is painfully slow
when using Python 2 (2.7 to be more specific) due to the
expensive and meaningless unicode conversions there (involved with
hot function calls like utf_8_decode).

With the following patch, my most complicated Python tools
finally have comparable performance between Python 2 and
Python 3. In the case of Python 2, some real-world Python scripts'
overall speedup can be as big as 34% (for my "lgcpath" command [3])
or even 57% (for my "lgcstat" command [4]). And from the new Flame
Graph [5], we can see that the corresponding function frames are
indeed gone.

Comments are welcome!

[1] https://github.com/openresty/nginx-gdb-utils#readme
[2] http://agentzh.org/misc/flamegraph/gdb-py-lgcstat-2015-0113.svg
[3] https://github.com/openresty/nginx-gdb-utils#lgcpath
[4] https://github.com/openresty/nginx-gdb-utils#lgcstat
[5] http://agentzh.org/misc/flamegraph/patched-gdb-py-lgcstat-2015-0113.svg

gdb/ChangeLog:

    * python/py-utils.c (python_string_to_host_string): use
    xstrdup directly for Python 2.
    * python/py-utils.c (gdbpy_obj_to_string): use
    python_string_to_host_string for both Python 2 and 3.
---
 gdb/python/py-utils.c | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/gdb/python/py-utils.c b/gdb/python/py-utils.c
index 58a5934..ed7be3b 100644
--- a/gdb/python/py-utils.c
+++ b/gdb/python/py-utils.c
@@ -209,6 +209,7 @@ python_string_to_target_python_string (PyObject *obj)
 char *
 python_string_to_host_string (PyObject *obj)
 {
+#ifdef IS_PY3K
   PyObject *str;
   char *result;
 
@@ -219,6 +220,9 @@ python_string_to_host_string (PyObject *obj)
   result = unicode_to_encoded_string (str, host_charset ());
   Py_DECREF (str);
   return result;
+#else
+  return xstrdup (PyString_AsString (obj));
+#endif
 }
 
 /* Return true if OBJ is a Python string or unicode object, false
@@ -245,12 +249,7 @@ gdbpy_obj_to_string (PyObject *obj)
 
   if (str_obj != NULL)
     {
-#ifdef IS_PY3K
       char *msg = python_string_to_host_string (str_obj);
-#else
-      char *msg = xstrdup (PyString_AsString (str_obj));
-#endif
-
       Py_DECREF (str_obj);
       return msg;
     }
-- 
1.8.5.6


             reply	other threads:[~2015-01-14  6:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-14  6:38 Yichun Zhang (agentzh) [this message]
2015-01-19 22:08 ` Yichun Zhang (agentzh)
2015-01-20 11:13   ` Phil Muldoon
2015-01-20 13:13     ` Joel Brobecker
2015-01-20 22:19       ` Yichun Zhang (agentzh)
2015-02-01 23:33 ` Yichun Zhang (agentzh)
2015-02-22 18:01 ` Yichun Zhang (agentzh)
2015-03-03 16:12 ` Joel Brobecker

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=1421217481-18204-1-git-send-email-agentzh@gmail.com \
    --to=agentzh@gmail.com \
    --cc=gdb-patches@sourceware.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