Time creating dataframes et al. separately from reading CSV #680
Assignees
Labels
Type: improvement
Better way of doing something
Comments
abelsiqueira
added a commit
to abelsiqueira/TulipaEnergyModel.jl
that referenced
this issue
Jun 27, 2024
Instead of using @Elapsed and saving the time inside EnergyProblem, use TimerOuputs. Time the inner parts of the EnergyProblem constructor. Closes TulipaEnergy#680
abelsiqueira
added a commit
to abelsiqueira/TulipaEnergyModel.jl
that referenced
this issue
Jun 27, 2024
To avoid changing the EnergyProblem structure too much because of timing, we create a timings dictionary. We time the constructor of EnergyProblem instead of the function that reads the CSV folder. This way we time the functions inside the constructor, which are the expensive functions in the input. Closes TulipaEnergy#680
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What and Why
The
create_energy_problem_from_csv_folderfunction times two calls:create_connection...which reads the CSV files into the connectionEnergyProblem(connection)which reads the dataframes input, creates internal structures and compute constraints partitions.Most timing should happen inside
EnergyProblem(connection), then it also shows when called directly.Possible Drawbacks
No response
Related Issues
No response
The text was updated successfully, but these errors were encountered: