(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. The C accelerator is now used by default. I already proposed to remove this benchmark: https://mail.python.org/pipermail/speed/2017-April/000554.html *but* Antoine Pitrou mentionned that the cloudpickle project uses it. Maybe we should try to understand what's wrong with _pickle (C module) for cloudpickle? Victor 2017-07-10 2:10 GMT+02:00 Bhavishya <bhavishyagop...@gmail.com>: > I was working on the two regressed benchmarks (i.e. pickle/unpickle > pure-python), and as it was a case with other benchmarks....that performance > is affected by import ...I thought that could be a case with pickle.py > too. And thus tried adding the above patch to Lib/pickle.py to measure the > initial import time. > > I haven't tried it for any practical use-case. > > > On Mon, Jul 10, 2017 at 5:27 AM, Victor Stinner <victor.stin...@gmail.com> > wrote: >> >> Sorry, I don't understand the direct link between the import time of 4 >> modules and the pickle module. Can you please elaborate? >> >> What are you trying to optimize? >> >> What is your use case? >> >> Victor _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
