Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
I icoads.utils
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • brivas
  • icoads.utils
  • Issues
  • #4

Closed
Open
Created Jul 06, 2020 by brivas@brecinosrivasMaintainer

profile_code.R review

This issue is mostly a discussion. To hear @dyb opinion on the function profile_code.R.

Basically the issue is that we must be careful when profiling the code, if we do it in big chunks for highly demanding task (e.g profile the entire new_merge_year_ids.R) we might find that in JASMIN for example, the resources will be more drain, the run will go slower and we can increase the time of runs forcing our jobs to stop or crash.

Therefore I created different functions to turn on the profiler and turn it back off. Saving the profiler data output to the same filename that you specify when you call the function. I also added a simple summary function, to read the output of the profiler and write it to a .csv

Cheers

Edited Jul 08, 2020 by brivas
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking