← All news
Seshat 1.8.5 fixes files in a third of the time after a check
Seshat 1.8.5 reuses the check made just before a fix and measures ink once, so a fix after a check takes about a third of the time.
By Rekhu
1 min read
The usual flow is: check the file, show the customer what was found, then fix. Seshat 1.8.5 makes the fix in that flow much faster.
What changed
- The check before a fix is not repeated. Seshat uses the check made in the hour before, when the file and the order are the same. Only the check's answer is kept for that hour, on Seshat's own server, never the file.
- Ink is measured once. Reduce ink takes its result (
under_limit, orpartlywith the places left) from the check that follows the fix, instead of measuring the ink itself as well. - Plates are separated while the other checks run, using a second processor.
On the Ghent PDF Output Suite test pages, a check followed by reduce ink now takes about a third of the time it took before.
Nothing changes in your code. The connectors already send the same order with the check and the fix.