This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients scoder, serhiy.storchaka, vstinner
Date 2016-08-23.21:15:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwbMYgfXTEWjZa_zusBJRMRzKjj2VH7SuuEJSJ3WL+f10Q@mail.gmail.com>
In-reply-to <1471974786.13.0.382183237353.issue27841@psf.upfronthosting.co.za>
Content
Stefan Behnel added the comment:
> If you care so much about C stack space, you could also try to create two or three entry point functions that keep (say) a 4, 8 and 16 items array on the stack respectively, (...)

I should compute statistics, but I'm quite sure that most function
calls take 5 or less parameters. I don't think that allocating 5
PyObject* uses too much C stack, what do you think?

I don't think that using the heap memory for more parameters will
"kill" performances. Python 3.5 already does the same, a tuple is
allocated in the heap memory ;-) It just that I want to optimize the
common case.
History
Date User Action Args
2016-08-23 21:15:00vstinnersetrecipients: + vstinner, scoder, serhiy.storchaka
2016-08-23 21:15:00vstinnerlinkissue27841 messages
2016-08-23 21:15:00vstinnercreate