[m-dev.] Proposing a new grade component.

[Paul Bone]

On Tue, Nov 08, 2011 at 02:16:59PM +1100, Julien Fischer wrote:
> 
> Given that it may have changed then I suggest you measure it again.
>

EXTRA_MCFLAGS = 
GRADE = asm_fast.gc
mercury_compile.01 average of 5 with ignore=1     14.10

EXTRA_MCFLAGS = 
GRADE = asm_fast.gc.profdeep
mercury_compile.03 average of 5 with ignore=1     75.55

EXTRA_MCFLAGS = --coverage-profiling
GRADE = asm_fast.gc.profdeep
mercury_compile.05 average of 5 with ignore=1     82.69

Note that none of these tests use --profile-optimized.

Test            | Time sec  | Slowdown      | Slowdown compared to dp
----------------+-----------=---------------+-------------------------
asm_fast.gc     |  14.10    | 1.00          | 5.36
dp              |  75.55    | 0.19          | 1.00
dp + coverage   |  82.69    | 0.17          | 0.91

Coverage profiling is about 9% slower than normal deep profiling.
Deep profiling is about 81% slower than normal execution,
and coverage profiling is about 83% slower than normal execution.

I compared to the cost of using deep profiling at all, coverage profiling does
not add much of a cost.

I'm going to do another test, I want to see what it's like when I compile the
library with profile optimized and compile the application (in this case mmc)
without profile optimized.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: Digital signature
URL: <http://lists.mercurylang.org/archives/developers/attachments/20111110/5fdde6f9/attachment.sig>