-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Runtime and memory profiling from logs #407
Labels
high priority
high priority issues
Comments
Which method did you use for the profiling? I have also tried to do some profiling. To build the analysis, I used the profvis({shiny::runApp('components/app/R')}, prof_output = 'profvis.html')
While running the app, I just loaded the example data a log out the app. This is what I got: Clearly, most of the time is spent on generating the different boards, which is normal. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We can profile startup time for different stages at startup and memory usage during startup from the log files. This enable us to compare different versions and different deployments. Below is an example for the master vs insertUI branch. What we need to do is insert in the stdout/stderr logs some timer start/stop points.
The text was updated successfully, but these errors were encountered: