Skip to content

Flops profiling per local kernel #669

@sv2518

Description

@sv2518

In the PR #668 I fixed the flop counting for our kernels. The FLOPS are counted per local kernel and then scaled up by the outer loops over the elements of the mesh. In the end, we only log the FLOPS for the global kernel.

It would be nice if we could log the numbers per local kernel so that someone (like me :)) who wants the FLOPS of a local kernel can just access them by reading the corresponding column in the summary that is printed when you pass in -log_view.

I don't have the time to work out how to do this correctly, I think we need to be careful that we don't accidentally add the FLOPS of the local kernels to the count for the global kernels in the logging process.

I will work around this for now by dumping the flops for my slate kernels in a file see https://github.com/OP2/PyOP2/tree/sv/dump-slate-flops

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions