plugin command optimizer #1

New Issue

Closed

opened 2019-07-10 14:54:16 +00:00 by luna · 1 comment

luna commented

2019-07-10 14:54:16 +00:00

Owner

currently the following script:

amp 5 1 8;
amp 7 4 2;
amp 80 70 10;
amp 80 73 20;
amp 80 75 20;
amp 80 76 20;

means we do 6 plugin loops, one for each plugin run.

we can speed this up by combining commands that relate to the same plugin, add their positions and parameters to a list, and then have something like Image.runPluginMulti.

we can either implement this on Runner or Lang. Implementing on Runner seems the simplest of the options, but implementing on Lang could be more extensible, however, I don't see of any other optimization case that can be done on the scripts.

currently the following script: ``` amp 5 1 8; amp 7 4 2; amp 80 70 10; amp 80 73 20; amp 80 75 20; amp 80 76 20; ``` means we do 6 plugin loops, one for each plugin run. we can speed this up by combining commands that relate to the same plugin, add their positions and parameters to a list, and then have something like `Image.runPluginMulti`. we can either implement this on `Runner` or `Lang`. Implementing on Runner seems the simplest of the options, but implementing on `Lang` could be more extensible, however, I don't see of any other optimization case that can be done on the scripts.

luna changed title from ~~optimizer~~ to plugin command optimizer

2019-07-10 14:54:36 +00:00

luna commented

2019-08-09 14:46:54 +00:00

Author

Owner

I was able to optimize plugin runs by making the tight main-plugin-run loop as small as possible, this isn't as required anymore.

luna closed this issue

2019-08-09 14:46:55 +00:00

No Label

No Milestone

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: luna/scritcher#1

No description provided.