When I simultaneously save as PDF from two different FM(10) instances, the Distiller becomes a bottleneck. FM starts only a single Distiller instance, which then processes the jobs one at a time. Is there any way to force FM to start a new Distiller instance for each "save" (and close it again when it becomes idle)?
Many thanks in advance for any input!
There is no user setting to change this behaviour. But if you delete the key (mentioned below) before starting the save operation from a new FM session, it will not use the same distiller instance.
Thanks for your help. Very highly appreciated indeed!
For whatever reason, I didn't have the "HKEY_CURRENT_USER\Software\Adobe\FrameMaker" key in my registry, but adding it (without subkey "DistillerInstance") changed behavior like you said it would. However, the Distiller seems to add the subkey at some point (on invocation?) so (to be on the safe side) perhaps I'll have to delete it before each "save as PDF"(?)
This begs a follow-up question, if you don't mind :-)
Can it be assumed that each Distiller instance will remain dedicated to the FrameMaker session that originally created it? I'm thinking along the lines of having a "pool" of FrameMaker sessions, each with its own dedicated Distiller instance.
You don’t need to delete the registry key before each Save as PDF (though it would not do any harm). FM adds this registry entry after invoking the distiller.
If the key is deleted before save as PDF by every FM session, every FM session will have a dedicated distiller instance.
Whatever Adobe pays you is not enough :-)
So you're saying that you only have to do the registry trick once for each FM session(?)
Perhaps you can clear up another mystery for me. Even after the Distiller has done its work, it can take a surprising long time (often several minutes) for the FDK's "save" function to finish. Why such a "lag", and is there any way to reduce it?
Thanks again for all your help!
You need to do this only once as long as the distiller is alive. After the distiller dies out, you will need to do it again before next save as PDF operation. A simpler approach would be to do it every time.
FrameMaker does some post processing on the generated PDF after the distiller finishes, which might be taking time. Specifically, the post-processing is needed if the document has rich media / U3D embedded in it.
If there is no such requirement, you can disable the post-processing clients in maker.ini file (/maker.ini) but this is not the recommendation. The clients are:
· FRAME2pdf – for 3D
· FMMediaAnnot – for rich media
· FMPDFReflow – for enabling some accessibility features in acrobat (Only for tagged PDF).