Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

6.6c slowdown

mcapel
Beginner
784 Views
After installing 6.6c compile times for all my projects have increased by a factor of 4-5 fold. Any ideas? The system in question is a dual athlon +2600
with 1 gig of ram.
0 Kudos
5 Replies
Steven_L_Intel1
Employee
784 Views
No clue. Haven't seen other reports of this and I haven't seen it myself.
Usually, a symptom like that means that you're "thrashing the pagefile" - if the compilation needs somewhat more virtual memory than you have RAM to support it, performance can suffer. You may want to try closing other programs while you're doing the compile to see if that makes a difference.
0 Kudos
tmcole
Beginner
784 Views

Check to see if you have array bounds checking turned on. This causes the observed increase in compile times over compiles without array bounds checking turned on for my code.

Steve was lookin into this issue well over a year ago, and the only response that I got back was "this is a complicated issue". Maybe Steve has an update as to the why there is such an increase in compilation time with bounds checking turned on for some codes.

0 Kudos
Steven_L_Intel1
Employee
784 Views
Sorry, I don't have any more information on the bounds checking issue. Intel Visual Fortran has a different implementation of that code, so I would not expect the problem to also appear there.
0 Kudos
mcapel
Beginner
784 Views
Steve:
I turned off all array bounds checking and in my project settings.
Compilation times are still 4-5 times larger than what they were before installation of 6.6C.
No changes in the system other that the 6.6C patch are involved in the observed slowdown. I.e. the page file size hasnt been modifiedcompared to when I was running 6.6B.
thanks,
mc.
0 Kudos
Steven_L_Intel1
Employee
784 Views
Sorry, I don't know what to tell you here... I don't know of any changes that would cause such a dramatic slowdown. You can send a sample compilable source to vf-support@compaq.com so HP can see if they can reproduce the problem, but it's not going to get fixed in CVF. I would be interested to see it (if you send it to vf-support, I will).
0 Kudos
Reply