Skip to content
This repository was archived by the owner on Jan 28, 2021. It is now read-only.
This repository was archived by the owner on Jan 28, 2021. It is now read-only.

Traces should be more granular #466

Closed
@erizocosmico

Description

@erizocosmico

There should be way more granularity in the traces. Right now, the only meaningful traces are the ones in the analyzer, because they're split per rule.

The execution traces take as much time as the last node, so they don't provide any meaningful insights when looking into which node is the one that's making a query slower.

Perhaps we should measure how much the Next in the iterators take as well. I'm worried that this might produce massive traces, though, for big datasets, but it's the only meaningful way to assess what node is making a query slow.

This is blocking src-d/gitbase#560 (comment)

WDYT @src-d/data-retrieval?

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions