Multi-threaded versus Single-threaded run time library

[wkramer]

Hello,

What is (are) exactly the downside(s) of always linking against the static multi-thread version of the run-time libraries?

Ibelieve that using the dll version leads to smaller applications and only one copy of the library routines will be loaded during runtime (is this correct?).

But how does multi-thread library affect performance of single-threaded applications?

I am using static libraries and DLL's that are used by various applications, some of which are multi- and others single-threaded.

It would make live a bit easier if I couldlink against one version of the run time libraries (except the difference between debug and release), but I don't want to sacrifice performance.

Walter Kramer

[TimP]

Only you can give an "exact" answer for your situation. A group I work with performs a few standard benchmark tests, and considers the threaded version satisfactory for single thread use if it doesn't sacrifice more than 5% performance. Much of that performance loss is at the application level, where a more efficient algorithm is available when not threaded.
As you hint, static linking against threaded libraries probably make the application much larger. How much larger is impossible to guess but easy for you to determine.

[wkramer]

Thanks Tim,

I guessed it would be up to me to say what is acceptable or not regarding size and performance,I just wondered if there was some other issueI was overlooking.

Walter