[pypy-dev] Unicode encode/decode speed

[Maciej Fijalkowski]

On Mon, Feb 11, 2013 at 7:39 PM, Amaury Forgeot d'Arc
<amauryfa at gmail.com> wrote:
> 2013/2/11 Eleytherios Stamatogiannakis <estama at gmail.com>
>>
>> >
>> > Which kind of profiler are you using? It possible that CPython builtin
>> > functions are not profiled the same way as PyPy's.
>>
>> lsprofcalltree.py .
>>
>> From APSW's source code, i think that it uses this API:
>>
>> (in cursor.c)
>> PyUnicode_DecodeUTF8
>>
>> Maybe lsprofcalltree doesn't profile it?
>
>
> Indeed. CPU cost is hidden in the cursor method.
>
>
> --
> Amaury Forgeot d'Arc
>
> _______________________________________________
> pypy-dev mailing list
> pypy-dev at python.org
> http://mail.python.org/mailman/listinfo/pypy-dev
>

I would suggest using valgrind. It's a very good (albeit very slow)
tool for seeing C-level performance. I remember seeing it both for
CPython and PyPy when trying. Can you try yourself?