Modeling and/or Model Manager and Solid State Drives?

[mrstero]

Has anyone out there been running any cocreate products on computers that have Solid State Drives (rather than Hard Drives).

Did you see any significant performance improvements How about reliability?

Thanks for your comments

Barry

[Shaba]

Yes i
Loading program is faster, ovsiully
And also load drawing
I never come back!
I have intel G2 SSD 80GB

[John van Doorn]

I'm running an intel postville 160GB.
It's very fast and runs very well with the CoCreate products.

[BMaverick]

If SSD drives are similar to USB jump/thumb drives, then take caution. One glitch and the drive can be whiped clean or the data corrupted/fragmented to the point of needing to re-format. ALWAYS make a good image of the installed and customized setup of the software on the SSD. This way, your down time is very little, if at all.

[mrstero]

Yes, reliability is the key concern.

Most PDM systems widely used today do not send EVERY save to a server - the user saves to local drive, then "checks in" periodically.

in the case of MM, at least here at my location, EVERY save goes to a server. Relatively speaking, that means there is a lot of disk IO activity going in, which in my understanding of things means that a "big win" could be realized by switching to SSD for such an application.

[neilwightman]

Normally MM only stores files locally during the save and load operation. During save the files are stored from Modeling, then transferred to the server and then deleted.

The Modeling save may be faster, but really most assembly save operations (unless they are very large assemblies) stay within the disk cache and don't even get written to disk.

Most of our save performance hit is actually applying the transaction in the database.

During load its normally spending the most time querying for the structure, files and masterdata. Not file downloading or reading. Well these are our findings from our performance tests which we run all the time, but silly things like virus scanners, bad shell extensions, graphics drivers and more can negatively affect performance.

Poor customisations are the worst thing for load and save performance in most real performance problems that customers / partners have reported.

[gmatelich]

Originally Posted by mrstero

Most PDM systems widely used today do not send EVERY save to a server - the user saves to local drive, then "checks in" periodically.

I've been thinking lately that it would be a cool enhancement if the CoCreate group were to offer a local version of the distributed file server, so each person could have fast loads of their local files. This would presumably greatly increase load speed of large assys, while still maintaining controls better than user based check ins. For small/medium businesses, it would probably be a lot cheaper than installing gigabit networking.

[frosendo]

Originally Posted by neilwightman

Most of our save performance hit is actually applying the transaction in the database.

Ditto for me.

We don't always have giglan or very high speed WAN connections but users closer to the db server have a great performance advantage over those who are further away even with local File Servers. Local FS's help but unfortunately not as much as we would like them too.