orko Posted April 20, 2008 Report Share Posted April 20, 2008 On one of our large projects, I'm converting all of our Call Library Function Nodes to accept dynamic paths to the same DLL - which may reside in different places on the user's computer after installation. We're pulling an installation path from the install out of the Windows registry and appending the DLL name to it, then passing this into the CLFN as opposed to having the path hardcoded like it has been. I haven't been able to find much info about the performance hit (if any) dynamically building these paths will cause in an application that may be calling this DLL in multiple threads at semi-reasonable (20Hz+) rates. Does anyone have experience with measuring this? I want to compare results, as my initial testing showed negligible difference...which surprised me. Sorry if the above isn't clear. I'm just trying to get a firm (but be gentle) grasp on what is happening "under the hood". Quote Link to comment
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.