I am migrating from Pro/INTRALINK to PDMLink 9.1 M010.
I am being told that for performance reasons, the target PDMLink environment needs to be limited to 3000 objects per folder, an object being defined as an iteration. The target PDMLink environment will be very large and many users worldwide, most being in the US.
The proposed solution is to automatically create numbered folders undereach productbased uponobject count. The proposed solution basically does away with using the folder structure to structure the data. This will require the users to search for their data rather than browse CS for it. As you can imagine, this will make migration very difficult and is guaranteed to make my users a ** little ** annoyed.
(1) Is there a performance impact when there are many object iterations in a folder?
I have folders in my Pro/I environment with 50-80k versions in them.
(2) If there is a performance impact, how have you dealt with this problem?
(3) Is there a best practice out there for managing large data sets in PDMLink?
Thanks in advance!
We're currently undergoing evaluation of 9.0, we've tried to limit all our folders to under 1000 objects. Only issue so far we've noticed with large folders is the time it takes to manually browse the folders if the display is set to all folder objects. What is instant in Intralink 3.x takes about 20 seconds with PDMlink. Most folks here are familiar with saved searches so manually browsing should not be an issue.
What is an issue for us is the display of real/decimal attributes. See my separate post a few post down in this group.