(Oops, I didn't notice that we started to talk off the list, let's
discuss that in python-dev please.)
I don't see the point of optimizing "pickle/unpickle pure python"
benchmark on Python 3. This benchmark doesn't make sense on Python 3,
since I don't know anyone using the pure Python pickle.
Please explain how to reproduce your benchmark. Maybe write a shell script?
Victor
Le 9 juil. 2017 17:49, "Bhavishya" a écrit :
> Hello,
>
> 1).I was going through the code of *python pickle* to search any
> optimization possibility.But the only thing that I found
I said about pure Python implementation (unpickle_pure_python),
because mail title is "Pure pickle bechmark".
INADA Naoki
On Mon, Jul 10, 2017 at 8:36 AM, Victor Stinner
wrote:
> Wait. Are we talking about the C accelerator or the pure Python
Wait. Are we talking about the C accelerator or the pure Python
implementation of pickle on Python 3?
Victor
Le 10 juil. 2017 01:19, "INADA Naoki" a écrit :
> I don't know this is relating to your case.
>
> When I saw Victor's report [1], I researched why Python 3 is
I don't know this is relating to your case.
When I saw Victor's report [1], I researched why Python 3 is slower than
Python 2 on unpickle_pure_python benchmark.
[1] https://mail.python.org/pipermail/speed/2017-February/000503.html
And I found Python 2 and 3 uses different version of pickle
Hi,
On Sun, 9 Jul 2017 19:38:09 +0530
Bhavishya wrote:
> Hello,
>
> 1).I was going through the code of *python pickle* to search any
> optimization possibility.But the only thing that I found very alarming was
> again the import time(I tried with lazy-import but it
On 2017-07-09 15:08, Bhavishya wrote:
Hello,
1).I was going through the code of *python pickle* to search any
optimization possibility.But the only thing that I found very alarming
was again the import time(I tried with lazy-import but it didn't helped
much.)
I found py3 to be ~45 times
Hello,
1).I was going through the code of *python pickle* to search any
optimization possibility.But the only thing that I found very alarming was
again the import time(I tried with lazy-import but it didn't helped much.)
I found py3 to be ~45 times slower on* initial imports(very raw