slow linking with new linker version

[Matthias Schuendehuette]

Hi everybody,

I have a strange linker issue here:

We link a binary on an Integrity Server (rx4640, 11iV2) with 'ld' B.12.47. This takes about 6 seconds.

Now we move to our new HP-UX 11.31 machine (a rx2660) with linker B.12.55. Here *exactly* the same linking lasts 3 minutes(180 sec !).

In both cases we link with the following options:

'ld +n -r -a archive '

All files are on local filesystems, so any network problems have no impact on the results.

During that long time on the new 11.31 machine, 'ld' stays on 'top' with 100% CPU...

Any ideas how to resolve this? Downgrade to the old linker version?

Thank you

Matthias

[Steven E. Protter]

Shalom,

Check for patches related to this issue.

You may find a patch for B12.55 that resolves this issue. You may need to report the issue and request a patch.

Downgrade is usually only good as an emergency option because in the end, you eventually will need the features provided by the newer version.

SEP

[Dennis Handly]

>We link a binary on an Integrity Server (rx4640, 11iV2) with 'ld' B.12.47. This takes about 6 seconds.
>Now we move to our new HP-UX 11.31 machine (a rx2660) with linker B.12.55. Here *exactly* the same linking lasts 3 minutes (180 sec!).

In order to compare apples to apples, install PHSS_41178 on your 11.23 system to see if it slows down.

>In both cases we link with the following options:
ld +n -r -a archive

Add -t to see how many objects are being processed.

>All files are on local filesystems

Thanks for that info.

>During that long time on the new 11.31 machine, 'ld' stays on 'top' with 100% CPU...
>Any ideas how to resolve this? Downgrade to the old linker version?

As SEP suggests, you need to contact HP so we can solve it.

I suppose you could use caliper on both versions to try to find where it is spending that 100% of time. And provide that data.

>SEP: You may find a patch for B12.55 that resolves this issue. You may need to report the issue and request a patch.

Unfortunately PHSS_41179 IS the latest patch.
So contacting the Response Center is the right way to get the problem resolved.

[Matthias Schuendehuette]

I installed PHSS_41178 on a 11.23 test-server and also copied the linker B.12.47 to that machine. Now verify that you're seating...

Linking with ld (12.47) 2.5 seconds (real)
Linking with ld (12.55) 5:24.4 (real)

324.4 / 2.5 = 129.76 (!!)

Something is really broken here... :-)

I should mention that 98% of the linking is done against ORACLE's 'libclntst9.a'.

The '-t' option delivers 2310 objects.

What is the 'response center'? Do you mean to open a call for the linker?

Thank you all so far!

Matthias

[James R. Ferguson]

Hi Matthias:

> What is the 'response center'? Do you mean to open a call for the linker?

The Response Center provides you an "inside" line for hardware and/or software support when you have a support agreement. This puts you in direct contact with HP engineers who can assist you in finding a resolution to your problem. You can open a case with the Support Manager web interface:

http://www.itrc.hp.com/service/mcm/homepageRequest.do

Regards!

...JRF...

[Dennis Handly]

>Linking with ld (12.47) 2.5 seconds (real)
>Linking with ld (12.55) 5:24.4 (real)

Thanks for the experiment. Were the CPU times as bad?

>The '-t' option delivers 2310 objects.

Can you cut down the numbers of objects such that it is easier to package for the lab but still duplicates the problem?

>Do you mean to open a call for the linker?

Yes.