jonathan-v Posted April 16, 2014 Report Share Posted April 16, 2014 Hello, For the most part we really love the asset management api. However, we are finding with large amount of assets(with multiple components) calling getComponents is proving to be crazy slow. For instance we have a render asset with 36 aov components. When we debug we notice it makes 248 calls to the server which seems unnecessary. We noticed this really only happens with getComponents. Ideally it would work similarly to getAssets which makes one call and returns the FTlist or maybe a dictionary. If there is possibly a better work around for this that we are missing would love to know your thoughts. ThanksJV Link to comment Share on other sites More sharing options...
Fredrik Limsater Posted April 16, 2014 Report Share Posted April 16, 2014 Hi Jonathan, yes, getComponents seems to do very unnecessary calls to the server. I will talk with the developers tomorrow to see what's going on and update this topic as soon as I know more. Sorry for the inconvenience. Thanks,Fredrik Link to comment Share on other sites More sharing options...
Martin Pengelly-Phillips Posted April 17, 2014 Report Share Posted April 17, 2014 Hi Jonathan, Thanks for the report. This issue stems from us trying to automatically bind an instantiated Component to a Location on retrieval for backwards compatibility. From a brief look at the code I can see a couple of ways to optimise this and also that we should give you the option to avoid the automatic location lookup when calling getComponents. We will tackle this in our next sprint that starts next week. cheers, Martin Link to comment Share on other sites More sharing options...
Martin Pengelly-Phillips Posted May 19, 2014 Report Share Posted May 19, 2014 Hi Jonathan, Just to update you that we have made some performance improvements here, but have a few more tweaks to do before releasing. Hopefully we should be able to get something out to you by end of next week at the latest. Martin Link to comment Share on other sites More sharing options...
katalina-w Posted May 19, 2014 Report Share Posted May 19, 2014 This is great news. We're looking forward to it. Thank you!Kat Link to comment Share on other sites More sharing options...
larsbijl Posted May 21, 2014 Report Share Posted May 21, 2014 Happy Days! looking forward to this Link to comment Share on other sites More sharing options...
Martin Pengelly-Phillips Posted May 28, 2014 Report Share Posted May 28, 2014 Hey all, Just to let you know that the performance improvement for getComponents is included in the new 2.6v4 release (http://support.ftrack.com/customer/portal/articles/1556180-2-6). You will also need to download a fresh copy of the API from your upgraded server. The time taken should now be significantly lower per getComponents call and only a few queries issued to the backend. Please let us know how it performs for you after upgrading. cheers, Martin Link to comment Share on other sites More sharing options...
jonathan-v Posted June 2, 2014 Author Report Share Posted June 2, 2014 This is a huge improvement!!! As mentioned above assets with 36 components used to take upwards to 8-9 seconds and we are now seeing the same asset returning in 0.6 seconds. Really appreciate the effort to get this optimized quickly. Thank you so much, JV Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.