|
| From: | Auto mailings of changes to Lily Issues via Testlilyissues-auto |
| Subject: | [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5949 Add option to use Ghostscript API instead of forking |
| Date: | Sun, 10 May 2020 11:59:12 -0000 |
commit ddfd0b4fb548aa32bfd809014502de0666d514f3 Author: Jonas Hahnfeld <address@hidden> AuthorDate: Mon Apr 27 20:54:43 2020 +0200 Commit: Jonas Hahnfeld <address@hidden> CommitDate: Sat May 9 20:04:45 2020 +0200 Issue 5949: Add option to use Ghostscript API instead of forking This is much more efficient than the current scheme when converting many PostScript files, for example when building the documentation. For the Notation Reference, lilypond-book now takes ~2m30s instead of 5m to compile all snippets from the notation.tely file. Other manuals benefit less, but still the time for 'make doc' on my system improves by one third from around 33m to 22m. An alternative would have been to always call gsapi_init_with_args with the same arguments used until now. This indeed works and avoids the overhead of forking, but the instance cannot be reused. Calling gsapi_new_instance -> gsapi_init_with_args -> gsapi_delete_instance for every conversion still means a lot of overhead and a prototype suggested only a small gain compared to the previous solution. This is not the default because recent versions of Ghostscript are distributed under the AGPL and it's unclear what the implications of linking to the library is. If built with support for the API, use -dgs-api=#f to still fork the gs command.
[issues:#5949] Add option to use Ghostscript API instead of forking
Status: Fixed
Labels: Fixed_2_21_2
Created: Thu Apr 30, 2020 07:12 PM UTC by Jonas Hahnfeld
Last Updated: Sat May 09, 2020 08:47 AM UTC
Owner: Jonas Hahnfeld
Add option to use Ghostscript API instead of forking
This is much more efficient than the current scheme when converting
many PostScript files, for example when building the documentation.
For the Notation Reference, lilypond-book now takes ~2m30s instead
of 5m to compile all snippets from the notation.tely file. Other
manuals benefit less, but still the time for 'make doc' on my system
improves by one third from around 33m to 22m.
An alternative would have been to always call gsapi_init_with_args
with the same arguments used until now. This indeed works and avoids
the overhead of forking, but the instance cannot be reused. Calling
gsapi_new_instance -> gsapi_init_with_args -> gsapi_delete_instance
for every conversion still means a lot of overhead and a prototype
suggested only a small gain compared to the previous solution.
This is not the default because recent versions of Ghostscript are
distributed under the AGPL and it's unclear what the implications of
linking to the library is. If built with support for the API, use
-dgs-api=#f to still fork the gs command.
http://codereview.appspot.com/548030043
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] |