Loading really large files?

[ugguy]

The machines at our main location are having a problem loading really large files. They say it takes about 40 minutes to load a large file, and sometimes it just crashes NX. There are 4 machines there, and all of them well exceed the NX system requirements.

Meanwhile, at our satellite location, I am able to export the same really large file in 12 minutes instead of 40. And though I get a message that says, "You have less than 30% of memory free", I continue the operation successfully.

The 4 machines at the main location are relatively new, 2 with AMD chips and 2 with Intel chips. All have 2 gigs of memory.

Here at the satellite location I am running a Dell 390 with an Intel Core 2 6600 @ 2.4Ghz, with 2 gigs ram.

Both locations are running NX 5.0.4.1

What could cause the difference in speed? cause it to crash? Any and all ideas welcomed...

Mike...

 

[cowski]

I would start by looking at the page file size (aka virtual memory).

 

[ugguy]

My page file is 2048.

I'll check what the main location is.

Thanks,

Mike...

 

[ugguy]

The page files from the main location is the same as mine, 2048.

Any other ideas? does NX have any configuration files that might deal with this?

Thanks,

UGGuy...

 

[looslib]

Are the files coming off a common server and if so, which location?
Are the files on local servers but with a different folder structure?
Are the files on a local drive?
Are you using TeamCenter or native fiing?
Are the load options set identically?
What graphics cards are in the machines?
Are you testing with the same file at both sites, saved at each site before testing?

2GB is minimal for NX. Try configuring a test machine with 4GB at location.
Pagefile should be 4096 and set min/max the same so Windoze doesn't try to dynamically allocate more space while loading the files.



"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

 

[ugguy]

The main office is still having a problem...

the files are being loaded off the local hard drive.

the tests are being run natively.

the load options are identical

both machines have the same graphics card (FireGL v3400)

Still looking for ideas...

Thanks...

 

[PHayden]

In your main office, is there a lot of applications using up some of your swap space?

We were having out of memory issues with 4GB of memory and with the 3GB switch set. We would crap out at ~2.8G
We upgraded to x64 with 6GB of memory and haven't had a problem since. PF Usage is 6.5GB as I type this. (creating a pdf of a large shaded view)
NX6.0.2.8 on HP xw9400.

 

[hudson888]

Mike,

If by large file you mean large assembly then try the following:

1. Turn ON partial loading in your load options

2. Also in your load options set your default reference set to lightweight or FACET.

3. Another setting for the load options would be STRUCTURE ONLY. In many cases you will eventually reach a point where you simply have to forgo opening large assemblies in their entirety.

4. If your assembly has just about reached the point where it may be too large to load all at once then structure your data so that you can find things without opening everything and/or use proximity filters where necessary.

Best Regards

Hudson

www.jamb.com.au

Nil Desperandum illegitimi non carborundum