Hi,

   Past few weeks we are faciing problems in Interplay searches. The size of the property store is around 100gb, which we feel is the reason for the Interplay to take time to do searches . Can anybody suggest a method to bring down the size of the property store

Regards,

Abhijit J.

Hi, 

I am feeling very sympathetic to what you are experiencing as we were on the same situation a month ago. It seems that the server avid certified for its databases can handle 5 million objects or 8 million with a ram upgrade to 9 GB and going to version 1.6.

We've been told that no faster hardware has been certified yet.

I am assuming that you have been on interplay since early versions which means that you have experienced very slow deletion times and bringing the system to a crawl every time you delete something which in turn means that you never managed to delete what you are supposed to...it was just impractical or there wasn't enough "quiet" hours in the day to allow deletion.

I am not sure if there is a way of making the property store smaller, we were told to just delete as much as we can from access. The problem is that once your database is of this size deletion is also slower.

We also asked avid if there is a way to run a script or something to delete from the property store anything older than xx.xx.xx but they said it can not be done. 

Luckily for us we also have an archive engine where we keep whatever is important to us. So we deleted the online database and created a new one.

We now have a brand new interplay database which is lightning fast. 

regards, 

G

Hello - We don't have a huge system but one thing I monitor is file count on our shared storage.  We have two interplay systems - one on ISIS and one on Unity.  I try to keep each workspace on these systems below a 10k file count.  If it exceedes this number, effeciency seems to decline.  We have around 30 workspaces and if the number hits that ceiling I start reducing file cout by deleting things like rendered effects.  They don't take up much drive space but help eleminate files.  for example I once deleted 15k of rendered effects which equaled 75MB of space.

Don't know if this helps or not. Our actual Interplay databases are less than 1GB each but our shared storage is 70TB.  We are a post house so we generate a ton of effects and such.

Hello!

The property store holds the AAF metadata, so it grows with the number of Avid Assets.
The best way to get this down again is - as already noted - to delete what is not needed anymore.
Common areas to check are Orphan Clips, Unchecked-In Avid Assets and rendered effects in general.

For deletion, there were some good changes with Interplay 1.6 (Clients and Engine).
There is a client update for 1.5.1 that speeds up deletion dramatically (Client Hotfix 1.5.1.1 that patches Interplay Access 1.5.1 to 1.5.1.10012).

Werner Bauer

Hi Abhijit,

Thanks for your posting!  There are a number of ways to keep the size of the property store in check, including keeping the metadata field contents short and deleting unneeded assets such as precomputes.  Have you contacted our technical support team about this?  Alternatively, please feel free to email me at sam.bogoch@avid.com.

Look forward to hearing from you,

Sam Bogoch

Director, Design for Production and Media Asset Management

Avid