On Tue, Apr 14, 2020 at 8:56 AM Jonas Hahnfeld
<[email protected]> wrote:
>
> 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.
>
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.
---
** [issues:#5907] Rewrite Mutable_properties based on vector<SCM>**
**Status:** Started
**Created:** Mon Apr 13, 2020 08:47 PM UTC by Han-Wen Nienhuys
**Last Updated:** Tue Apr 14, 2020 07:34 AM UTC
**Owner:** Han-Wen Nienhuys
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.
https://codereview.appspot.com/575990043
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list._______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
