Strange behavior - affects performance
-
I've an in-proc COM object that is registered on the client PC from a network share. An app that uses this COM object running out the same network share shows marked performance degradation (upto 2-3 times slow) when compared to running the same app with the COM object registered locally (the dll was copied to a local drive). Neither the app nor the the COM object access any files over the network other than some initial setup that happens at load time. I was expecting a delay only during app load time compared to the local install case, but it turns out that as the network traffic increases, the app starts to lag behind in processing time sensitive events (sometimes upto 20 minutes behind!). Also interesting to note is that as the network traffic reduces, the app starts to catch up & events get handled in timely fashion. Anybody experienced similar behavior wrt COM objects being registered from a network share? Any insights? Chen Venkataraman