-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
3D Tiles demo has terrible imagery performance #4166
Comments
One thing to try is turning |
Even in Chrome, compare these:
If you, for example, quick and dirty select the "Half Dome" view, it is clear that it loads faster in 1.24. Perhaps this is as simple as default parameters being too conservative? Or are we not making as many requests as we think we are....or the wrong ones? We need to address this before merging #3476. |
Maybe it's just my computer, but I'm running both branches locally and the results are about equal on Chrome and IE. Do you notice it working better when |
Either way I will look more into this. |
I would definitely make sure you start with a clean cache while working on this; it will exaggerate the problem since latency of requests is probably a big factor here. |
Clean cache or just use dev tools to throttle the speed. The cache was warm and still noticeable for me. |
Turns out this is also a problem in I guess the bigger question is by is disabling fog producing such poor performance for a straight down close up view? |
Add |
@bagnell can you please look at this when you have time? Ideally before 1.25 next Thursday. |
Perhaps now duplicate with #4359. |
I doubt it's a duplicate, since shutting off fog is what causes the behavior in this issue and turning it back on fixes it. |
In my machine, loading the 3D Tiles example in IE 11 and without ever moving the camera, it takes over a minute for all of the imagery to come in. If I use the same default view (below code snippet) but without 3D Tiles loaded, it only takes a couple of seconds. I'm not sure if this is a problem with the new request scheduler or something unrelated. I actually see a similar issue in Chrome but it's much faster (several seconds vs instant rather than a minute vs a few seconds).
The text was updated successfully, but these errors were encountered: