🌱 Enrico's Digital Garden

Metrics refactoring

2 min read

Components

Select Connection: INPUT[inlineListSuggester(optionQuery(#area)):connections] Date Created: INPUT[dateTime(defaultValue(null)):Date_Created] Due Date: INPUT[dateTime(defaultValue(null)):Due_Date] Priority Level: INPUT[inlineSelect(option(1 Critical), option(2 High), option(3 Medium), option(4 Low)):Priority_Level] Status: INPUT[inlineSelect(option(1 To Do), option(2 In Progress), option(3 Testing), option(4 Completed), option(5 Blocked)):Status]

What is currently wrong?

There are many issues in the metrics storing.

  • if index is loaded from file, the build metrics are not stored (still todo) ✅ 2025-03-10
  • build metrics should be a separate table ✅ 2025-03-03
  • the only way to see the metrics is through the sql database
  • k and delta now are defined before building the index → no independent runs with different k and delta ✅ 2025-03-10

solution:

  • rewrite the sql database, with build metrics separated from the search metrics

  • index file should store inside the necessary metrics, so they can be added to the corresponding table if there is the need

  • print for summary, csv for compatibility

  • per lo storage delle build metric in teoria non serve salvarle in una struct separata → aggiunge un overhead di performance ma sti cazzi (meglio che farlo alla fine). La funzione poi funzionerebbe sia se costruisco l’indice, sia se faccio il load da file

build metric

  • funzione per salvare in modo indipendente che sia da file o buildato ✅ 2025-03-10
  • controllare nel processo di build ✅ 2025-03-03
  • fare il salvataggio delle metriche da file ✅ 2025-03-10
  • [ ]

Graph View