On Thu, Jun 18, 2020 at 06:49:13PM +0100, Barry Scott wrote: > The key part of the idea is that the memory holding the ref count is > not adjacent to the memory holding the objects state. Further that > rarely modified state should be kept away from usually modified state.
Isn't that going to play havoc with modern CPU pipelines and pre-fetching? Every time a function is called, there will be cache-misses galore and performance plummets? I know very little about how this works except a vague rule of thumb that in the 21st century memory locality is king. If you want code to be fast, keep it close together, not spread out. https://stackoverflow.com/questions/16699247/what-is-a-cache-friendly-code When I'm programming at the Python level I don't need to worry about any of this (and in fact I can't do anything about it), but I expect that for the C implementation, that will be pretty critical. -- Steven _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/JN4ABC4TEPODGRKQL4B7MHUHUW7NFDJD/ Code of Conduct: http://python.org/psf/codeofconduct/
