Editing Content via the IFS

cgoodall

Hello,

We're running TS 6.7 on Windows 2003 EE. I've been tasked with hunting down some performance issues.

We have several developers who edit content almost exclusively through the IFS. They have the IFS share mapped on their PC's and use either Dreamweaver or Homesite to browse and edit files.

Is there any reason that such access to the IFS should not be allowed?

It seems like this method of editing could cause more traffic than necessary. Instead of touching a file twice (on download and again on upload via the local file manager), a file being edited is open across the network and TeamSite has to 'handle' every time the user saves their work. Also, some of these apps may be intermittently polling for updates in the directory tree on the IFS.

Thank you in advance for your input.

Sincerely,
~Chris

nipper

I used mapped drives often, with no trouble. The performance should be similar to a mapped drive, certainly not fast, but seldom horrid. What type of performance issues are you seeing ?

You mention 6.7, is this worse that before the upgrade from 6.whatever ?

Now some IDEs like to take control of the complete directory structure so they touch hundreds of files and directories (looking for images, css, etc). That may have something to do with it.

You may want to write a script to do a recursive find through out the iw-store and see how long it takes to run from the local filesystem and from a mounted drive. Use Perls benchmark to see how the time compares.

HTH

Andy