Issue 524062: USE_CACHE_ALIGNED still helpful? (original) (raw)
Issue524062
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.
This issue has been migrated to GitHub: https://github.com/python/cpython/issues/36185
classification
Title: | USE_CACHE_ALIGNED still helpful? | |
---|---|---|
Type: | Stage: | |
Components: | Interpreter Core | Versions: |
process
Status: | closed | Resolution: | fixed |
---|---|---|---|
Dependencies: | Superseder: | ||
Assigned To: | jackjansen | Nosy List: | jackjansen, tim.peters |
Priority: | normal | Keywords: |
Created on 2002-02-28 21:53 by tim.peters, last changed 2022-04-10 16:05 by admin. This issue is now closed.
Messages (3) | ||
---|---|---|
msg9465 - (view) | Author: Tim Peters (tim.peters) * ![]() |
Date: 2002-02-28 21:53 |
Jack asked for this report: """ MacPython uses it. At the time it was put in it caused a 15% increase in Pystones because dictionary entries were aligned in cache lines. But: this was in the PPC 601 and 604 era, I must say that I've never tested whether it made any difference on G3 and G4. Put in a bug report in my name, and one day I'll get around to testing whether it still makes a difference on current hardware and rip it out if it doesn't. """ | ||
msg9466 - (view) | Author: Jack Jansen (jackjansen) * ![]() |
Date: 2002-04-11 21:49 |
Logged In: YES user_id=45365 As MacPython normally uses the standard MSL malloc nowadays (and will probably use pymalloc in the future) the benefit of USE_CACHE_ALIGNED has disappeared. I've removed it. | ||
msg9467 - (view) | Author: Tim Peters (tim.peters) * ![]() |
Date: 2002-04-11 21:57 |
Logged In: YES user_id=31435 Since Jack removed this moldy old symbol, closing this as Fixed. |
History | |||
---|---|---|---|
Date | User | Action | Args |
2022-04-10 16:05:03 | admin | set | github: 36185 |
2002-02-28 21:53:42 | tim.peters | create |