- May
- 3,515
- 5
I am interested in how TCC starting performance is affected by the absence
or presence of plug-ins and their location (i.e., the absence or existence
of a PLUGINS subdirectory). Assume for this inquiry that any already loaded
DLL is in physical, internal memory, and not paged out (else all kinds of
issues not related to TCC come into play).
Case 1
------
TCC is started from the desktop or the quick launch bar. Plug-ins are
autoloaded from the PLUGINS subdirectory. Is this faster if another
concurrent TCC session has already loaded the plug-ins?
Case 2
------
TCC is started as a pipe from another TCC instance, which has already loaded
the plug-ins. The new instance does not utilize any plug-ins. Does the pipe
start faster if there is no PLUGINS subdirectory than if there is?
If in either of the above cases there is a difference,
--
Steve
or presence of plug-ins and their location (i.e., the absence or existence
of a PLUGINS subdirectory). Assume for this inquiry that any already loaded
DLL is in physical, internal memory, and not paged out (else all kinds of
issues not related to TCC come into play).
Case 1
------
TCC is started from the desktop or the quick launch bar. Plug-ins are
autoloaded from the PLUGINS subdirectory. Is this faster if another
concurrent TCC session has already loaded the plug-ins?
Case 2
------
TCC is started as a pipe from another TCC instance, which has already loaded
the plug-ins. The new instance does not utilize any plug-ins. Does the pipe
start faster if there is no PLUGINS subdirectory than if there is?
If in either of the above cases there is a difference,
--
Steve