search

HPCE / hpce-2017-cw5

1 stars 6 forks source link

hold_time performance check issue #57

Open SKarolcik opened 6 years ago

SKarolcik commented 6 years ago

So our group didn't receive a graph for hold_time. I was fixing some AWS compilation issue yesterday and initially supposed that the test was done on the previous check-in and that's why it failed. Unzipping the log files however left me with this:

Running hold_time

n = 50.000000 * (5:1:+inf).^2.500000 SysLogLevel = 3 -> 3 UserLogLevel = 1 -> 1 [bench_puzzle/sys], 1511381527.88, 2, Created system console log at logLevel=3. [bench_puzzle/sys], 1511381527.88, 2, Created user console log at logLevel=1. [bench_puzzle/sys], 1511381527.88, 2, Created user file log at file '../../logs/DeusExGPU/2017-11-22-blah/hold_time.user.log' with logLevel=3. [bench_puzzle/sys], 1511381527.88, 2, Total time budget = 30.000000, start=1511381527.876126, deadline=1511381557.876126

[bench_puzzle/sys], 1511381527.88, 2, Time budget used = 0.000008, remaining = 29.999992 [bench_puzzle/sys], 1511381527.88, 2, Iteration i=1 -> scale=4409 [bench_puzzle/sys], 1511381527.88, 2, Creating random input

[bench_puzzle/sys], 1511381527.88, 2, Puzzle::Execute starts TIMEOUT CPU 33.28 MEM 10842160 MAXMEM 10842160 STALE 0 MAXMEM_RSS 43412

Looking at this, it compiled and ran it once and then some sort of timeout happened? The version runs on AWS for me, so I wonder if I am missing something here. Is there a way to replicate this?

SKarolcik commented 6 years ago

Nevermind, looking at it again it did not execute a single time. Regardless, my older version of code was not compiling at all under AWS. There are no errors in compilation report for this one so it might be the fixed version and therefore it is hard to pinpoint the issue.

m8pple commented 6 years ago

The log says that it is this commit:

### Last commit message is:
commit 25b287af2eb7e877352217521375ebe46f4622e6
Author: xxx <xxx@ic.ac.uk>
Date:   Wed Nov 22 17:20:37 2017 +0000

    kernel loading removed from mining execute function

Do you mean that you don't know how to tell which commit you made is causing the compilation problem? You can always check out each version, then try compiling each one (and bisect if necessary).