Skip to main content
A
anagnost1-Visitor
1-Visitor
March 2, 2011
Question

ProE delays when working dir is on a network drive

  • March 2, 2011
  • 10 replies
  • 6063 views

Hello all,

we are facing the following strange behavior.

We are running 3 licenses of ProE (WF 4 M140) without intralink or any other PDM system. We are storing our models on a network file server and the users work exclusively there.

What we have noticed is that the performance of ProE (eg regeneration time) depends on the number of files that the working directory holds. The more files on the working directory, the more time the regeneration needs!!!

Am I missing something here?


Thanks in advance.

Vassilis Anagnostopoulos




This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

10 replies

J
JonathanHodgson13-Aquamarine
13-Aquamarine
March 9, 2011

We have noticed that, when running Pro/E from a network drive, there can be a delay in opening a menu when you haven't used that menu for some time. Once the menu is loaded, it seems to be cached and then loads instantly.

We hadn't noticed the regeneration time issue; we've just tested it and couldn't measure any difference (~18sec regen time, 1016 files vs 124). We haven't tested moving the .prt file to different directories, though.

Where are your trail.txt files being written? Your system may run faster if you write them to a local hard disk; if you're writing them to the (network) working directory then perhaps that has an effect.

A
anagnost1-VisitorAuthor
1-Visitor
March 9, 2011

... yes, our trail files are stored locally to c:\temp.

I will explain you, how my test procedure is, just in case you want to give it a try.

1. Set a working directory locally, say to c:\temp

2. Create a simple part with two features, one protrusion and one cut.

3. Suppress the cut feature

4. Resume the cut feature and measure the time the model needs to regenerate and update the geometry (it should be almost instantly).

5. Keep the part model in memory, don't erase it.

6. Set a working directory somewhere in the network. This network folder must have as many ProE files as possible. (in my case they are about 5000)

7. Suppress the cut feature

8. Resume the cut feature and measure the time the model needs to regenerate and update the geometry (in my case this is about 4 seconds!).

I would be really thankful, if you can make a short test like this and inform me about your findings.

Thanks a lot for you time and effort.

J
JonathanHodgson13-Aquamarine
13-Aquamarine
March 9, 2011

Hi Vassilis,

I've just done the test exactly as you describe.

In both cases the regen time was too short to measure. The biggest working directory I could find was the one with 1016 files, though.

WF4.0 M110 on XP32 Pro 2002 SP3, by the way.

All the best,

Jonathan

C
creodential10-Marble
10-Marble
December 14, 2015

This is odd, and I guess my answer is ..uh..suitably odd.

Back in the days we experienced similar problems with Proe2001 / Win XP when working with Intralink via a Novell based network. Suppressing a feature in a simple part took about 30 seconds on a mid-range machine. Even after a fresh start you could find files in your object list (Files - Manage Session - Object list) with no relation whatsoever.

This did the job: Changing the config.pro setting "browser_favorite" to the same path as the working folder (might want to work with a variable in your start script there) and deleting all other paths that were linked as favorites since all the objects there to be found were loaded and monitored by the system.

HTH

Andreas

Terms & ConditionsAccessibility statement