Hi guys,
We have been experiencing some slowness while navigating through shotgun. While troubleshooting, we noticed that disabling Tank integration removes the slowness and allows Shotgun to behave at normal (fast) speeds. This feels like a recent change though, maybe in the past week or so. Did something change that would have caused Tank integration to greatly slow down normal Shotgun browsing (loading new pages, etc.)?
Hi Greg.
Nothing changed on our end, but a slowdown could be related to your filesystem. The Tank integration reaches out to the filesystem through either the Java applet or our browser plugin to try and determine which menu options to provide (i.e. launch Maya, launch Nuke, create folders, etc.). Do you have your Toolkit install on a network/shared disk or local? Is filesystem performance otherwise working as expected on your side with whichever storage the Toolkit install is on?
Ryan.
Hey Ryan,
Sorry for the delay, I'm trying to get some more information to work with but it's still just an intermittent annoyance rather than a huge show-stopper. Our toolkit install is on a network, but we haven't really noticed any different performance there recently nor have we made any major changes. Actually using toolkit inside of Maya for example still behaves normally. We've setup new permissions controls on our filesystem, but I can't imagine that would have an impact on everyday Shotgun usage. To clarify, we are not always talking about the actions that query (launch Maya, create folders, etc.), but simply navigating to an assets page seems slower. Throughout the day there is probably some variation in our network traffic, so maybe that is a factor. It's possible we just notice it more in Shotgun because that's primarily what we're using in web browsers.
You say "...through either the Java applet or our browser plugin...", does this mean that we have an option in how we have tank integration running? Maybe I can found out which method we are using, and test the other?
Hi Greg.
Yes, you do have an option in terms of using the browser plugin or the Java applet. The way Shotgun handles this is it first checks to see if the browser plugin is installed and enabled. If so, it uses the browser plugin. If that isn't available, it then tries to use the Java applet. If that isn't available either, you'll get an error.
To check this, have a look at what plugins you have enabled in your browser. For Chrome, you go to the URL chrome://plugins. For Firefox, you go to Tools > Add-ons. And, for Safari, you go to Help > Installed Plug-ins.
Ryan.