Cost of extra libraries

On Mon, 2004-04-12 at 11:51, Enrico Weigelt wrote:

> If your application uses the functionality, then it has to import 
> the library providing it. Other applications not using it have no need
> to import the lib and so dont require it to be installed on the system.
> Putting distinct functionality into distinct modules is IMHO a MUST
> for modern software development. System installations should only contain
> exactly those code which is really needed. Unneeded extra code wastes
> resources, adds unnecessary complexity and brings unnecessary points
> of failures, errors, leaks.

You might want to investigate the performance implications of extra
modules for ELF shared object ... the most common object file format 
on systems where GLib is used. (Linux, Solaris, FreeBSD, etc.)

A symbol resolution is essentially a hash table lookup *per* shared
library, so adding entry code to a shared library doesn't increase the
cost of looking up symbols, but adding extra libraries does. 

And modern operating systems will generally be able to keep unused
code from being loaded at all.


Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]