.wf folder size

[EricHuffman]

Gurus,

Is there a maximum size for the .wf folder? How big can this get before
Pro/E starts hanging?

I am usually pretty good about keeping clean workspaces but right now I
have over 8 active workspaces and my .wf folder is 11GB. This morning
Pro/E is running painfully slow so I'm wondering if this is the reason.



Wildfire 4.0 Datecode m140

Windchill 9.0 Datecode m030





Thanks,

Eric

[davehaigh]

In the config.pro you might have this setting, dm_cache_limit. If it's set to anything other than 0 you may run into problems as cache approaches the limit that was set. It can cause ProE to become non-responsive.

dm_cache_limit sets a size limit for the local cache

You may also want to go to Tools, Server Manager, Pick the Cache tab, Pick Cache Tools, select on the server so all your workspaces are available. At this point you can pick on individual workspaces and clear the cache on just that one workspace.

David Haigh

[leger.xavier.pr]

Hi Eric,

When you clean up your workspaces, or delete it, the local cache is not updated (it won't reduce in size).

Only Tools > Server Manager > Cache > Clear cache, as adviced by David, will reduce the local cache amount.

If your WS is really clean (no New Locally or Locally Modified objects), you can also delete the .cache2008 folder that resides inside the .wf folder. Next time you'll access to your WS with ProE, it will download all needed content to the local cache.

This advice is valid for WF4 and Windchill 9.1 M040 , I don't know if it's applicable to 9.0

Best Regards

Xavier

Gurus,

Is there a maximum size for the .wf folder? How big can this get before
Pro/E starts hanging?

I am usually pretty good about keeping clean workspaces but right now I
have over 8 active workspaces and my .wf folder is 11GB. This morning
Pro/E is running painfully slow so I'm wondering if this is the reason.



Wildfire 4.0 Datecode m140

Windchill 9.0 Datecode m030





Thanks,

Eric

[davehaigh]

Removing the .cache2008 folder may be ok if you have the config option dm_upload_objects AUTOMATIC

If you are not using that option you run the risk of deleting locally modified files that have not been uploaded.

When you look into the cache folder, you will see files that start with "lid_" and "sid_". The lid_ files are locally modified, they may or may not be uploaded.

Before doing such a drastic thing as deleting the folder, I would copy the entire folder to another backup location. There is also a utility that will rename all/most of the lid_ files to the original ProE names.

David Haigh