haskell / haskell/ThreadScope

Interpreting foreign functions call information as activity

Ouverte
#60 4 commentaires 1 réaction 0 personnes assignées Voir sur GitHub
enhancement
Langage dominant
Haskell
Étoiles
173
Forks
37
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

Feature request

It'll be great if time between:
"HEC YY: stopping thread ZZZZZ (making a foreign call)" and
"HEC YY: running thread ZZZZZ" where YY and ZZZZZ are same between events and intepret as a single foreign call.

Activity diagram to show it as this thread is doing something foreign and this could be shown as separate coloured activity inside HEC graphs for YY execution unit.

This is a time spent somewhere else, but affecting us as we have to wait for it at this thread, so it's kind of activity albeit it is outside Haskell. It's time spent in foreign call which will be useful to be represented and measured.

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Piste de recherche

Start by locating the event handling for “stopping thread ... (making a foreign call)” and the matching “running thread ...” message. Trace how these events become HEC activity diagrams, then define completion as showing the interval as a distinct foreign-call activity that can be measured.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
haskell
Domaine
data-visualization, performance
Type d'issue
Fonctionnalité
Difficulté
4/5
Temps estimé
3-5 jours
Activité
À l'abandon
Clarté
Plutôt claire
Accessibilité débutants
35/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.