Startup times after using fastbind.

[Robert Wells_3]

G'day,

We are using fastbind on incomplete executables that have been built specifying deferred for the runtime binding mode. They are written in C++.

We have measured the startup times for these servers and we have seen that the initial startup times are of the same order as when starting servers that have not had fastbind run on them.

After this initial boot, the startup times drop dramatically, e.g. from 1 minute 20 seconds to approx. 20 seconds.

It is almost as if the fastbind info in the server is considered stale and needs to be rebuilt. But I know that the shared libraries have not been modified at all.

We have measured this many times and it is always the same. After linking and using fastbind, the initial boot of the server is always slow. Any subsequent boots are very fast.

Does a 'fastbind' server cache anything in the incomplete executable when it is first started?

Any thoughts would be gratefully received.

cheers,
Rob

[ranganath ramachandra]

the fastbind tool writes the fastbind information into the executable itself and nowhere else. this happens only when the fastbind tool is run. running the executable subsequently does not result in collecting information etc.

any effects of fastbind should be felt only when running the applications in question. however i dont see why it should make execution slower (it wont have anything to do with system startup unless you ran fastbind on applications involved in system startup).

please do mention the OS release and version of fastbind (linker/loader patch) installed.

[Robert Wells_3]

G'day,

Thanks for the reply. I should have been a bit clearer. When I say boot times I mean the startup times for these servers. They are Tuxedo servers and we usually talk about booting the servers.

We are running HP-UX 11i. Our patch level for the linker tools is quite old and will be patched in the near future.

regards,
Rob

[ranganath ramachandra]

hello,

if you can please let me know whether the application is PA32 or PA64, i will check it up and get back to you.

thanks & regards
ranga

[Robert Wells_4]

G'day,

It is PA64. We are using:

aCC: HP ANSI C++ B3910B A.03.52
92453-07 linker command s800.sgs ld PA64 B.11.33 REL 020603
ld: 92453-07 linker linker ld B.11.33 020617

cheers,
Rob