Use @timeit on function calls

[gnawin]

Related issues

Closes #934

• Remove EnergyProblem.timings
• Use @timeit on function calls

Checklist

• I am following the contributing guidelines

• Tests are passing

• Lint workflow is passing

• Docs were updated and workflow is passing

[abelsiqueira]

LGTM, thanks @gnawin !

[gnawin]

@abelsiqueira @datejada After checking the time log log.txt for the Tiny case, here are a few observations:

• create_interna_structures is 27.6% of the time, which seems mostly spent on the functions related to reading tables (e.g., TulipaIO.get_table, DBInterface.execute). Probably there is nothing we can do better, but interesting to see.
• compute_dual_variables is 3 times more expensive than total solver time. Seeing the code, it makes sense, but still, good to realize.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.83%. Comparing base (73f765e) to head (60da05b).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #956      +/-   ##
==========================================
- Coverage   95.91%   95.83%   -0.08%     
==========================================
  Files          29       29              
  Lines        1027     1008      -19     
==========================================
- Hits          985      966      -19     
  Misses         42       42              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[abelsiqueira]

Nice insights. We should definitely do that as part of the efficiency improvement for the EU dataset

[datejada]

Thanks @gnawin; the compute duals will change once we change how to store the solution and hopefully, it will be faster than the current approach 😄