-
Notifications
You must be signed in to change notification settings - Fork 25
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
Resolves 1473: Improve load times after changes from within Docker container #1474
Resolves 1473: Improve load times after changes from within Docker container #1474
Conversation
Dibs on Linux! |
90af438
to
00f39a1
Compare
…Webpage into 1473-dev-environment-slow-to-update-javascript-files
…Webpage into 1473-dev-environment-slow-to-update-javascript-files
I didn't experience any performance degradation on Linux. Works just fine!
The link does not work (404 error) |
@misaugstad can you try https://drive.google.com/file/d/1YpCilah2rhffCqGSYcIN6Fw5pfZ9QLS_/view? seems like github took the trailing underscore out of the hyperlink lol. |
Yep that works! |
…Webpage into 1473-dev-environment-slow-to-update-javascript-files
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't experience any performance degradation on Linux. Works just fine!
cool. do we have reviews from Windows and Mac users? |
I believe @shivenbhatt is doing Windows and has started but not finished reviewing. Haven't found a Mac user yet (but was waiting until we deployed to Newberg before I really pushed it on anyone else). |
i'd suggest having a mac user test it now as originally this issue was reported by @aileenzeng who is a mac user. |
@misaugstad @athersharif I can test on Mac! I’m in-between tasks atm and have some time now |
Yep! To change JavaScript files, it probably takes about ~20 seconds on my computer to make the change and reload the page (which is significantly better than what it was before!). In comparison, I think it takes about 15 seconds with the old setup.
Changing |
It takes a while longer to update JavaScripts on this new branch for windows. On this branch it takes around 40-60 seconds, on the develop branch it took around 10-12 seconds. |
I'll also try to test on Windows myself this week. |
It seems that the :delegated flag is mainly intended as a performance tuning measure for Mac users (as shown in this docker documentation https://docs.docker.com/docker-for-mac/osxfs-caching/). For me (Mac), I'm getting very good speed ups, with my compile time for javascript changes taking before around 2-3 min and now averaging ~10 seconds. Similarly, for the sbt compile, I'm noticing it's now taking around ~15 seconds compared to the 1-2 min prior to testing this flag. |
Wow, that's huge. Thanks!
…On Mon, Jun 15, 2020 at 7:13 PM ThatOneGoat ***@***.***> wrote:
It seems that the :delegated flag is mainly intended as a performance
tuning measure for Mac users (as shown in this docker documentation
https://docs.docker.com/docker-for-mac/osxfs-caching/). For me (Mac), I'm
getting very good speed ups, with my compile time for javascript changes
taking before around 2-3 min and now averaging ~10 seconds. Similarly, for
the sbt compile, I'm noticing it's now taking around ~15 seconds compared
to the 1-2 min prior to testing this flag.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1474 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAML55JHL3GT6DFJCB4FC3LRW3IKRANCNFSM4GX2NV2Q>
.
--
Jon Froehlich
Associate Professor
Paul G. Allen School of Computer Science & Engineering
University of Washington
http://makeabilitylab.io
@jonfroehlich <https://twitter.com/jonfroehlich> - Twitter
Help make sidewalks more accessible: http://projectsidewalk.io
|
I was running into (15sec - more than a minute) load times with the occasional extremely long load time of about 3 min. I fixed this issue by allocated more CPUs and memory to the docker container, through docker desktop. The changes for the docker container were 1 CPU -> 4 CPUs and 2GB memory -> 4 GB memory, though I suspect the CPU is what made the difference, not the memory. Load times are now under 10 secs. Running on macos big sur 11.2.1, docker version 20.10.2 |
fixes #1473.
following #1364 (comment), this is a change to improve the load times after changes from within the container. this is a workaround to an issue that Docker for Mac has, and like every workaround, this should be thoroughly tested on other OSs as well. :)
we'd need to test:
here's a screen recording on Mac after this change (let me know if the link doesn't work): https://drive.google.com/open?id=1YpCilah2rhffCqGSYcIN6Fw5pfZ9QLS_