Rewrite Mutable_properties based on vector<SCM>
Alists use are based on linked lists. They have poor locality, which
introduces more CPU cache misses. Since LilyPond is not multithreaded,
the CPU sits idle during these misses.
This is part a series of experiments to rearchitect property
storage. None of them seem especially promising currently.
Han-Wen, is this already meant for review? If not, I propose to either delete it right away or correct title and description and set it to Needs_work.
set to needs_work is fine.
On Tue, Apr 14, 2020 at 8:56 AM Jonas Hahnfeld
hahnjo@users.sourceforge.net wrote:
Related
Issues: #5907
I'll add parenthesis: "I propose to either (delete it right away) or ((correct title and description) and (set it to Needs_work))". So setting to needs_work alone wasn't exactly one of my options.
On Tue, Apr 14, 2020 at 8:56 AM Jonas Hahnfeld
hahnjo@users.sourceforge.net wrote:
what does 'delete' mean? Given the related discussion about
performance,, I think this code is useful to keep around in case
anyone wants to opimize get_property again.
My though was to delete this issue on SF (not talking about Rietveld), which you didn't create for the first upload. Doesn't matter anymore, I've added the missing title and description.
Diff:
Diff: