(3) Preview multiple record layout will corrupt a document making it useless forever with no hope of repair if one mistakenly saves it. Unmanagable sized datasets seem to resulted in non-linear growth of processing time. It takes 0.7 seconds per record when handling a quantities than seem manageable to ID. And 20,000 records, before some image size reductions that may have impacted results, once took over 48 hours before I aborted the session. By this I mean even a data set of 5,000 records takes along time to process. (2) Indesign cannot handle moderately large datasets. (1) Mail merge was not engineered to the prevailing standard of quality at Adobe. The process is clearly cpu-intensive, but minimally multi-threaded. This provided little benefit, proving the problem is not disk intensive. I have plenty of workspace on a RAID 5 array and have even tried running the entirely project of a 10gb ram disk that held all source files and was designated as the scratch disk. Basically, only about two processors out of 32 are doing much. Nor am I processor constrained in a way that is avoidable as most of my cpu's are not being assigned tasks. I have ruled out the possibility of my needs being RAM constrained as Task Manager indicates significant memory headroom at all times. Even if it were, there is plenty of room to argue my situation is not large or massive in scale, but no greater than medium. I say non-exotic, because I can bring to mind hundreds of documents I have seen in the world that are far more complex, and nothing in the marketing or documentation suggests InDesign is limited to small-scale projects. I have spent hundreds of hours inventing workarounds and optimizations to get an entirely non-exotic data merge to work involving only two documents. I still have a live unresolved issue whose defining characteristic I have yet to discovered. I posted this following a link labelled "contact us." Adobe does not monitor the World Wide Web 24x7? How do foreigners get tech support? I paid my money and expect an official response. This is my second try with the same result.
WTF is going on? This document usually composes at a rate of 0.7 records per second. And the result has posted behind the progress bar. 56 records, 24 hours, and still only 98% completed.
0 kommentar(er)
