|From:||Auto mailings of changes to Lily Issues via Testlilyissues-auto|
|Subject:||[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5797 Do not run GC after processing every file.|
|Date:||Sun, 01 Mar 2020 08:29:09 -0000|
Patch on countdown for March 3rd
[issues:#5797] Do not run GC after processing every file.
Created: Wed Feb 26, 2020 09:39 AM UTC by Han-Wen Nienhuys
Last Updated: Sun Mar 01, 2020 08:28 AM UTC
Owner: Han-Wen Nienhuys
When processing multiple files, we ran GC between the files. The
motivation was that we use a conservative garbage collector, so we get
the most accurate scan when our stack is small. We never measured the
impact of this idea.
On every GC, we pay the cost of tracing through the live set,
ie. fixed data that spans multiple files, and by forcing GC calls, we
trace that data more often than necessary.
We get CPU time savings of ~20 % by not forcing GC.
For GUILE 1.8, the following timings for running "make test-baseline"
on my development branch
force GC on every file
let the GC decide when to collect
For GUILE 2.2, the difference is similar.
Sent from sourceforge.net because address@hidden 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 address@hidden https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
|[Prev in Thread]||Current Thread||[Next in Thread]|