Skip to content
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

Hot code reload times #9

Open
kevohagan opened this issue Jan 22, 2015 · 6 comments
Open

Hot code reload times #9

kevohagan opened this issue Jan 22, 2015 · 6 comments

Comments

@kevohagan
Copy link

Hey guys, this is not really an issue.

i was just wondering what is your view on the subject. pulling in all the core-elements + paper-elements of polymer gets consistant 10+ sec hot code reload times.

Do you guys have any advice on this? :)

@spencercarli
Copy link
Contributor

I wonder if it's caused by the vulcanize package... it's compiling or adding the various polymer components to the project on every server restart so that could be adding to the time a HCR takes.

Having everything concatenated is great for deployment but can cause added time during dev. Not entirely sure if that's what is causing it though

@schnie
Copy link
Contributor

schnie commented Jan 23, 2015

Vulcanization is skipped in development. It just adds the contents of
imports.html to your head tag, where they would normally be. I also
thought it may be the culprit, so I removed the package and just added them
to the head like normal, but the sluggish performance remained.

It may have something to do with the file-watcher doing too much work
watching all the polymer components, I'm not sure. It does seem to get
progressively worse on each dev restart, so it seems like some sort of
leakage.

I've been working only in polymer apps lately, do build times get slower
over time with non-polymer projects, or is this only happening in
polymer/web-components projects?

On Fri, Jan 23, 2015 at 9:00 AM, Spencer Carli [email protected]
wrote:

I wonder if it's caused by the vulcanize package... it's compiling or
adding the various polymer components to the project on every server
restart so that could be adding to the time a HCR takes.

Having everything concatenated is great for deployment but can cause added
time during dev. Not entirely sure if that's what is causing it though


Reply to this email directly or view it on GitHub
#9 (comment)
.

@hellogerard
Copy link

Have witnessed this too. It definitely gets slower with each restart, so
agree on the leakage.

It also seems MUCH worse in Safari than Chrome, which points to a Polymer
issue.

But it seems to slow down before the browser refresh. Once the page starts
reloading, it feels normal. That points to a meteor issue. Could be wrong
on this.

File watcher is a good theory.

On Friday, January 23, 2015, Greg Neiheisel [email protected]
wrote:

Vulcanization is skipped in development. It just adds the contents of
imports.html to your head tag, where they would normally be. I also
thought it may be the culprit, so I removed the package and just added
them
to the head like normal, but the sluggish performance remained.

It may have something to do with the file-watcher doing too much work
watching all the polymer components, I'm not sure. It does seem to get
progressively worse on each dev restart, so it seems like some sort of
leakage.

I've been working only in polymer apps lately, do build times get slower
over time with non-polymer projects, or is this only happening in
polymer/web-components projects?

On Fri, Jan 23, 2015 at 9:00 AM, Spencer Carli <[email protected]
javascript:_e(%7B%7D,'cvml','[email protected]');>
wrote:

I wonder if it's caused by the vulcanize package... it's compiling or
adding the various polymer components to the project on every server
restart so that could be adding to the time a HCR takes.

Having everything concatenated is great for deployment but can cause
added
time during dev. Not entirely sure if that's what is causing it though


Reply to this email directly or view it on GitHub
<
https://github.com/Differential/polymer-demo/issues/9#issuecomment-71196484>

.


Reply to this email directly or view it on GitHub
#9 (comment)
.

@vkammerer
Copy link

Try removing the "meteorhacks:inject-initial" package. I did it and it stopped reloading all assets as before.

@kevohagan
Copy link
Author

Removing meteorhacks:inject-initial hasnt really changed much for me..

btw on hot code reload on cordova i get :

android:http://meteor.local/packages/autoupdate.js:192) METEOR CORDOVA DEBUG (autoupdate_cordova.js) start dowloading /bower_components/web-animations-js/test/blink/interpolation/transform-rotate-interpolation.html

etc etc for all files in public directory (all the files of each component directory including demos and all)

anyone knows how i can change that?

@schnie
Copy link
Contributor

schnie commented Feb 11, 2015

I haven't seen these issues in a while since upgrade meteor. On
[email protected] now and reloads seem back to normal.. for our app at least.

On Wed, Feb 11, 2015 at 4:05 AM, kevohagan [email protected] wrote:

Removing meteorhacks:inject-initial hasnt really changed much for me..

btw on hot code reload on cordova i get :

android:http://meteor.local/packages/autoupdate.js:192) METEOR CORDOVA DEBUG (autoupdate_cordova.js) start dowloading /bower_components/web-animations-js/test/blink/interpolation/transform-rotate-interpolation.html

etc etc for all files in public directory (all the files of each component
directory including demos and all)

anyone knows how i can change that?


Reply to this email directly or view it on GitHub
#9 (comment)
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants