Hi,
I made a workflow with imported images directly from an url. 15 images per record and productions of 4000 tot 10000 records. The pdf are getting really big. Really big…
After optimizing the pdf file in acrobat I managed to reduce the size greatly.
Is there a way to save the pdf as optimized pdf directly from the workflow?
I understand and I’m not trying to be difficult… but…
I posted this question: Optimize Embedded Images
That is the issue I’m trying to overcome. Pres Connect cleans up after itself and that is very nice. But this happens after the whole workflow process is done. Due to a limited space I can’t run big productions without the workflow crashing (well not really crashing, it just stops). I use the emulation an splitter to secure multiple parts of a big datafile.
But I stil run out of memory before the whole production is done. I got no answer on the other question I posted and also our local Pres Connect provider in the Netherlands couldn’t find the answer. So I’m looking for a work around. So cleaning the cache after a splitted cycle could be the answer. If the temps are deleted before the next split starts, the limited disk space would not form a problem.
Any advice?
You mention memory issues and disk space issues. Are they both occurring or do you simply mean that you are running out of disk space?
Yes running out of disk space
You could try running each of your PDF files through the Create PDF task, in Workflow. You would set the Document option to None and tick the Optimize Resulting PDF option.
Note that this option attempts to optimize the PDF but may not necessarily succeed in doing so (in some cases, it may actually increase the size of the PDF!), but it’s something you can try.
One other option you can try: after you’ve sent each PDF to its intended destination, use a Create File task, which will replace the current work file (the PDF) with a new file that contains just a few bytes. This will ensure that even though temporary files still remain on disk until the end of the process, their size will be very small and should no longer be a concern. Note that using this option may have a slight impact on overall performance.
Let me know if that helps.
Thanks both sound like very good option. I’m going to try them out and get back at you. Thanks for explaining! <3
I don’t think this is going to be the solution for me… the first option isn’t really making the pdf smaller. the second option, I’m not sure if I meet the results.
In the my design there a lot of images (jpg) that are imported with an external url in the img-tag. I see that all of these images are stored in my filestore folder as pdf. My filestore looks like this and growing, a whole lot of images in pdf and very big merged-files. these are steps of 10 records and I god like 5000.
Most of these remain there after a loop and after the sesion is done. So before my run is complete my harddisk is full and the production aborts.
Files in the filestore are typically under the control of Connect’s clean-up service. This can be set to clean up fairly soon to reduce the number of files that’s kept there.
Having said that, you should at least have sufficient disk capacity to hold those intermediate files while the run is ongoing. If that’s not the case, I am afraid there’s not much else to do then reduce the size of your run.
You can mark content sets for deletion after your run is complete (that’s a separate task in Workflow), and if the clean-up service runs soon after, they should be gone after that.
One thing that may help, is to reduce the size of the images so they match your printer’s capabilities (or the screen) as well as possible. But perhaps that has already been taken care of.
