On https://www.solidworks.com/sw/support/shareyourscore.htm the best T3500s are slower (see attached image)!
But I don't know if all the tests are reliable, because there are very low values in this table and the configurations of this one don't seem that far from yours!
After that, maybe wanting to open an assembly of 100,000 parts in solved is simply not possible!
The error comes from the fact that Assembly Xpert crashes my SW every time. So I created a BOM and then added it all up in Excel to know my total number.
1- No Realview enabled
2- The assembly is divided into fifteen sub-assemblies, certain of 6000 pcs.
3- The 2013 version was more stable, but not better in the context of mega assembly.
4- The coins are on a server
5- No tooltip appears when opening or while I push the machine all the way up.
When we talk about crashes, graphical bugs, delays in zooming and other manipulations, just a small rectangle that is displayed when rotating and then returning to normal when you let go of the middle button... or simply don't come back.... one of the first tests to be carried out is to activate the "Emulate OpenGl functions" option (it can be found in the performance options, and can only be activated if no file is opened...
So for an almost identical config no worries in sw2014 SP1 on a Dell Precision T3500
The small differences I have:
2 300GB discs in raid 15000 towers for the OS and software part (original disc)
1 256GB SSD disc for the project folder and split to have the library.
Graphics card nvidia quadro 3800
The big problem on this machine is the location of the ECC memory sticks. Depending on the location, this slows down the system and causes crashes (especially in the case of a dual processor).
The solution is to mix the strips in such a way as to have a balance in the slots and if possible avoid slot 3 if the number of strips is less than the number of slots.
The opening of the 5000 parts assembly is not a problem if you set to light.
I also have a T3500 and we also work on our company's network.
When you get to large assemblies, there is a lot of background work to be done.
Here are some ways to improve the fluidity of large assemblies:
- check that some components have not lost their paths (this generates high latencies because SW is trying to find them);
- Look at the calculation time of the parts (you can save a lot by removing all the functions with end condition until the next surface, repetition function, etc...)
- Complex assembly can help but with some constraints;
- Currently I'm testing the block bar but too early to give an opinion.
@gt22 the two disc 15000 was originally supplied with the machine bought second-hand and modified for one of my customers. So little investment in the machine apart from the RAM and the SSD.
It remains a respectable and stable machine for a small price
In my personal config I run with 2 SSDs 500GB for the system and 250GB for the short projects and 2 good old WD green and blue discs for archiving
There are several of us who work in a network on different subassemblies of the main assembly, so a copy to the hard disk is impossible.
I've attached an example of the recurring graphical bug that we didn't have with the 2013 version, so this is basically the reason why I find SW 2014 to be inadequate and brings me more problems than solutions for a fairly high price.