Hi adepters,
We've been living with major performance problems with Epic Editor for some time, but it only seems to get worse. Our problem centers around several "books" that have 700 or more file entities. Everything is defined either in a master document or in a parameter entity file (most of the file entities are shared amongst all of these books). It is often necessary to open the master document and we're finding that it takes anywhere from 15 minutes to an hour for this to occur. The fast time of 15 minutes is achieved only by moving everything onto a local Windows drive and avoiding any network involvement. Does anyone know why this is taking so long or if there is anything we can do to speed it up? We're using Epic 4.4 on Windows XP/2000 machines, most of which are around 750 MHz processor and 256 MB memory (although 512 MB memory doesn't seem to help). Disk space isn't a problem. It seems as though Epic is accessing every file during its initialization. Any way to eliminate that or speed it up? I've tried launching the Epic command with -nocc specified, but has no affect.
Anyone have any ideas?
Dave Hintz
UGS PLM Solutions
We've been living with major performance problems with Epic Editor for some time, but it only seems to get worse. Our problem centers around several "books" that have 700 or more file entities. Everything is defined either in a master document or in a parameter entity file (most of the file entities are shared amongst all of these books). It is often necessary to open the master document and we're finding that it takes anywhere from 15 minutes to an hour for this to occur. The fast time of 15 minutes is achieved only by moving everything onto a local Windows drive and avoiding any network involvement. Does anyone know why this is taking so long or if there is anything we can do to speed it up? We're using Epic 4.4 on Windows XP/2000 machines, most of which are around 750 MHz processor and 256 MB memory (although 512 MB memory doesn't seem to help). Disk space isn't a problem. It seems as though Epic is accessing every file during its initialization. Any way to eliminate that or speed it up? I've tried launching the Epic command with -nocc specified, but has no affect.
Anyone have any ideas?
Dave Hintz
UGS PLM Solutions