Repository navigation
Use calloc in set resizing #66229
Description
| BPO | 22030 |
|---|---|
| Nosy | @rhettinger, @vstinner |
| Files |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = 'https://github.com/vstinner'
closed_at = <Date 2014-07-22.08:06:02.206>
created_at = <Date 2014-07-22.07:32:08.867>
labels = ['performance']
title = 'Use calloc in set resizing'
updated_at = <Date 2014-07-22.08:06:02.205>
user = 'https://github.com/rhettinger'bugs.python.org fields:
activity = <Date 2014-07-22.08:06:02.205>
actor = 'rhettinger'
assignee = 'vstinner'
closed = True
closed_date = <Date 2014-07-22.08:06:02.206>
closer = 'rhettinger'
components = []
creation = <Date 2014-07-22.07:32:08.867>
creator = 'rhettinger'
dependencies = []
files = ['36024']
hgrepos = []
issue_num = 22030
keywords = ['patch']
message_count = 3.0
messages = ['223638', '223640', '223641']
nosy_count = 2.0
nosy_names = ['rhettinger', 'vstinner']
pr_nums = []
priority = 'normal'
resolution = 'rejected'
stage = 'patch review'
status = 'closed'
superseder = None
type = 'performance'
url = 'https://bugs.python.org/issue22030'
versions = ['Python 3.5']
Activity
rhettinger commentedon Jul 22, 2014
Victor, how does this look?
vstinner commentedon Jul 22, 2014
Be careful. In my tests, calloc() was slower than malloc() + memset() for
memory blocks smaller than 1 MB. Calloc() can be interesting if only a few
pages (4096 bytes) are modified.
You must provide benchmarks.
vstinner commentedon Jul 22, 2014
See also issue bpo-21644 (bytearray).