search

bdkjones / CodeKit

CodeKit 3 Issue Tracker
https://codekitapp.com
82 stars 5 forks source link

remarkable initial load time #141

Closed katerlouis closed 8 years ago

katerlouis commented 8 years ago

(Unfortunately I can't recall since which beta the problem occurs or if it was there all the time?)

Whenever I open the project for the first time it takes around 30-90 seconds to acutally paint something. This happens locally in Safari, Chrome or the iOS Simulator, no matter which address I choose (localhost:5757, jimbo.local:5757, the ip:5757)

This also happened in 4 different network / router enviroments both locally and remotely on other devices.

I've got a notion that you need more information for that. Tell me what you need and I'll provide quickly.

This issue is kinda embarrassing when you already hyped a client with this cool feature for collaboration in fine tuning, where I make changes and they see live updates in there browser! ;) And then it takes forever to load :O

".. hmm – .. weird weather these days, huh?"

subhaze commented 8 years ago

Curious if you've inspected the network panel to check for any blocking assets. Such as sync loading fonts from some fountry, some form of analytics, some kind of CDN, etc... Basically anything that could be loading in sync and failing/loading horribly long.

bdkjones commented 8 years ago

Last time someone wrote to me with this issue, we spent 3 days and countless emails going back and forth and it turned out that the guy had set Chrome to mimic dial-up speeds. You don't, by chance, have Chrome set to mimic dialup speeds, do you?

Are you using an external server with these projects? If so, what's the result when you try to preview a project that does NOT use an external server? If that loads instantly, then the delay is between your external server and CodeKit.

You should also google "slow loading of localhost etc/hosts file" and look at those results---many people have faced this issue and found that editing the hosts file fixes it.

@subhaze's comments are also a good place to start. Inspect the network traffic.

Finally, give it a shot on a completely separate Mac if you can. Since no one else is reporting the issue, this must be something isolated to your machine.

katerlouis commented 8 years ago

No font-service, no analytics, no CDN. No Chrome mimic dial up speeds (what ever that is :D) The issue seems to be in every browser.

I use MAMP Pro for php and databases. It seems that is the cause. When I go to villmar:8888 it loads freakin fast. When I go to jimbo.local:5757 it takes forever–

but only the first time After the "wall" is surpassed it goes as fast as usual. And from then on it is fast in every browser. So it feels like "after sleeping" CodeKit needs some time to talk to MAMP?

(I don't know what has to happen to trigger the delay again, so I have to wait to show the network panel– although I'm pretty sure it's the communication to MAMP)

That wasn't always the case and I hope so much that we can solve this issue.

d279a515-bf1d-4dbc-b6b2-9a351c000e8d
bdkjones commented 8 years ago

No, the problem isn't CodeKit. The problem is your Mac resolving the address of the external server. You said this same delay happens with the non-bonjour preview addresses?

Sent from my iPhone

On Aug 2, 2016, at 03:47, René Eschke notifications@github.com wrote:

No font-service, no analytics, no CDN. No Chrome mimic dial up speeds (what ever that is :D) The issue is in every browser.

I use MAMP Pro for php and databases. It seems that is it. When I go to project:8888 it loads freakin fast. When I go to jimbo.local:5757 it takes forever–

but just the first time After the "wall" is surpassed it goes as fast as usual. And from then on in every browser. So it feels like "after sleeping" (I don't know what has to happen to trigger the delay again) CodeKit needs some time to talk to MAMP?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

katerlouis commented 8 years ago

Yes, it also happens with localhost:5757 and <MY IP>:5757 Any ideas what I can do? :(

bdkjones commented 8 years ago

Can you test a different Mac?

katerlouis commented 8 years ago

Don't have a different and my colleagues are wining about installing MAMP :D Anyhow: If it works on another Mac with CK3 and MAMP all we would learn is that it has something to do with my specific setup, which we already assume to be true :D

Until we have another idea I try to find a Mac which is not busy with shitloads of projects!