First post so be gentle......
Currently we have a graphic development center in Texas that is using Photoshop Creative Suite 2 Version 9.0.2. They are creating .eps and .tif files. Our publishing group is in New Jersey using InDesign Creative Suite 2 Version 4.0.4. The .indd and associated linked files are on the Texas server. All filed are opened on the remote server, scratch disks and other temp files live over the network link in the Texas server.
So as you guessed the files open very slowly, typically our .indd’s are 6 to 10 meg with 150 to 300 links. The eps and tif files are 140 K to 16 meg max. So opening the files is around 3 minutes. We then create a postscript file so we can pump the output to Adobe Distiller 7.0 and this postscript process is between 7 and 10 minutes. Very stressful in crunch time.
Our alternative is packaging the files up and this has its own set of issues.
My question has been asked before, but what can be done to assist in improving the speed of operations? We have tested moving just the .indd files over to the hard drive or a local New Jersey server and now the files crash due to link errors and time outs. Average ping test on a 32 byte file is 47 ms from Texas to New Jersey. So slow but not that slow.
Local .indd work in Texas accessing the same server locations is 17 seconds to open and 30 second to create a postscript file. Ping is 5 ms. So if you do the math, it still should not take 10 minutes to spool up a postscript over the net.
Any ideas would be great things like pointing the virtual scratch disk locally, or a good content management process to copy/mirror art to another server but do not loose control of the version. Thanks in advance.
Currently we have a graphic development center in Texas that is using Photoshop Creative Suite 2 Version 9.0.2. They are creating .eps and .tif files. Our publishing group is in New Jersey using InDesign Creative Suite 2 Version 4.0.4. The .indd and associated linked files are on the Texas server. All filed are opened on the remote server, scratch disks and other temp files live over the network link in the Texas server.
So as you guessed the files open very slowly, typically our .indd’s are 6 to 10 meg with 150 to 300 links. The eps and tif files are 140 K to 16 meg max. So opening the files is around 3 minutes. We then create a postscript file so we can pump the output to Adobe Distiller 7.0 and this postscript process is between 7 and 10 minutes. Very stressful in crunch time.
Our alternative is packaging the files up and this has its own set of issues.
My question has been asked before, but what can be done to assist in improving the speed of operations? We have tested moving just the .indd files over to the hard drive or a local New Jersey server and now the files crash due to link errors and time outs. Average ping test on a 32 byte file is 47 ms from Texas to New Jersey. So slow but not that slow.
Local .indd work in Texas accessing the same server locations is 17 seconds to open and 30 second to create a postscript file. Ping is 5 ms. So if you do the math, it still should not take 10 minutes to spool up a postscript over the net.
Any ideas would be great things like pointing the virtual scratch disk locally, or a good content management process to copy/mirror art to another server but do not loose control of the version. Thanks in advance.