[issue1747670] Limiting data copy in xmlrpclib

Changes by Serhiy Storchaka : -- status: open -> pending ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue1747670] Limiting data copy in xmlrpclib

Changes by Stefan Krah : -- nosy: -skrah ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue1747670] Limiting data copy in xmlrpclib

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue1747670] Limiting data copy in xmlrpclib

Serhiy Storchaka added the comment: Yes, it would be nice if you provided an example. -- ___ Python tracker ___ ___ Python-bugs-list

[issue1747670] Limiting data copy in xmlrpclib

Gael Le Mignot added the comment: It's not something that can be easily benched because it depends a lot of the use case. If some conditions are present (big amount of data sent to XML-RPC, the XML-RPC server taking a long time to answer, end either Python giving back the memory to the OS or a

[issue1747670] Limiting data copy in xmlrpclib

Serhiy Storchaka added the comment: Do you have any benchmarks? -- nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-li

[issue1747670] Limiting data copy in xmlrpclib

Thomas Fenzl added the comment: I removed the unnecessary check on single-element arrays. No strong opinion on usefulness, as I don't use xmlrpc a lot... -- Added file: http://bugs.python.org/file29579/xmlrpc_less_copy-1.diff ___ Python tracker

[issue1747670] Limiting data copy in xmlrpclib

Gael Le Mignot added the comment: Great that join does the optimisation by itself now, but the last issue of the patch (cleaning the _data array before calling f() so the memory of _data can be collected earlier) still seems meaningful today. -- ___

[issue1747670] Limiting data copy in xmlrpclib

Antoine Pitrou added the comment: I would close this as out of date, unless you have other suggestions to improve memory consumption. -- ___ Python tracker ___ ___

[issue1747670] Limiting data copy in xmlrpclib

Antoine Pitrou added the comment: Well, str.join() already optimizes this case to avoid copies: >>> s = "x" * 50 >>> id(s) 139712615414000 >>> id(''.join([s])) 139712615414000 -- nosy: +pitrou ___ Python tracker

[issue1747670] Limiting data copy in xmlrpclib

Thomas Fenzl added the comment: Adapted the patch to python3.3 It may be useful with large amounts of transfered data avoiding a copy and freeing memory earlier. The functionality is tested with the existing unit tests. -- nosy: +Thomas Fenzl versions: +Python 3.4 -Python 2.7 Added file

[issue1747670] Limiting data copy in xmlrpclib

Mark Lawrence added the comment: Could somebody update here please http://svn.python.org/view/*checkout*/python/branches/py3k/Misc/maintainers.rst -- ___ Python tracker ___ _

[issue1747670] Limiting data copy in xmlrpclib

Changes by Martin v. Löwis : -- assignee: loewis -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue1747670] Limiting data copy in xmlrpclib

Stefan Krah added the comment: Martin has recently removed his name from py3k/Misc/maintainers.rst. Also, he has stated that assigning bugs to him might mean that they get less attention (due to the large number of issues that he's involved in). -- nosy: +skrah

[issue1747670] Limiting data copy in xmlrpclib

Mark Lawrence added the comment: The code in the patch has been removed from py3k. This can only go forward if a unit test is provided. Change assigned to as per maintainers list. -- assignee: -> loewis nosy: +BreamoreBoy, loewis versions: -Python 3.1 _

[issue1747670] Limiting data copy in xmlrpclib

Changes by Daniel Diniz : -- stage: -> test needed type: -> resource usage versions: +Python 2.7, Python 3.1 ___ Python tracker ___ __