Local versus network

Hi,

This is likely old news to many, but since it bit me I thought I'd pass it along. This week I deployed FMS for the first time. It's my first experience working with FM on a network. Most of my energy has gone into making sure the files had redundant backups and some security issues. Over the last two days I noticed that a couple of files were taking forever to close. Both these files had "Closer" scripts that called a number of Cleanup scripts, each of which involved potentially substantial finds. On a powerful desktop machine the files would close in the blink of an eye. On the network one of them took two or three minutes to close. So I ran the script debugger to find the bottlenecks.

It turns out that the Cleanup scripts were written early on in the development of this solution and since then I had, since the arrival of script triggers and other improvements, managed to have virtually every task these scripts accomplished occur in the normal operation of things eg. before the file closed. So it was a simple matter of disabling several Perform Script steps after examining the offending scripts.

This (some would say trivial) experience has given me a completely new understanding of development and a heightened respect for the pro developers out there (I am not one).

The files now close in the (ok, network) blink of an eye.

Rick.