[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxaxp::vmsnotes

Title:VAX and Alpha VMS
Notice:This is a new VMSnotes, please read note 2.1
Moderator:VAXAXP::BERNARDO
Created:Wed Jan 22 1997
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:703
Total number of notes:3722

119.0. "incremental linker?" by HYDRA::PASHAPOUR (Disk space, the final frontier) Thu Jan 30 1997 14:04

    Hi,
    
    An ISV is asking for an incremental linker for Alpha VMS. Is there such
    a thing? They are using "vector something" now but need an automated
    way of doing it.  Their sharable library is about 60 MB and takes about
    50 minutes to link on VMS. As a result, they are doing more and more
    work on UNIX boxes, even though 90% of their revenue is from VMS.
    
    Apprecaite your help in advance.
    
    Amin
T.RTitleUserPersonal
Name
DateLines
119.1No Incremental Linker, Are They Using Shareables?XDELTA::HOFFMANSteve, OpenVMS EngineeringThu Jan 30 1997 14:1915
   There is presently no incremental linker for OpenVMS, though dynamic
   linking is possible via the image activator and logical names, or via
   the use of the lib$find_image_symbol dynamic-activation routine.

   As an alternative, I'd suspect these folks need to look at moving to
   shareable images (if they're not already using them) or increasing the
   number of shareable images (if they are using them), and at the linking
   process itself, as well as at the process working sets and quotas.

   For customer-visible information on shareable images, see:

     http://www.partner.digital.com/www-swdev/ -
	pages/Home/TECH/faqs/ovms/ovms-shexe-cook.html

119.2When is the last time the linker process was tuned?EPS::VANDENHEUVELHeinMon Feb 03 1997 16:2114
    
    They may also want to look into optimizing their link environment a
    little. It may well be time to defrag the freespace on the linker
    target output disk, and how fragmetned are the input OBJs, OLBs?
    Does the process running the linker still have adequat Working set
    params or is it stuck at a few Mb defined many moons ago? Just check
    the old CPU time versus elapsed time, IO counts, Pagefaults and the
    likes. Fortunate enough to have a performance monitor going with
    hot-file display? Perhpas create a DECram disk for popular linker
    input files? Default file extend size bumped from 5 to 100 or so?
    and so on...
    
    	Hein.