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

3D Tiles demo has terrible imagery performance #4166

Open
mramato opened this issue Aug 2, 2016 · 11 comments
Open

3D Tiles demo has terrible imagery performance #4166

mramato opened this issue Aug 2, 2016 · 11 comments

Comments

@mramato
Copy link
Contributor

mramato commented Aug 2, 2016

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).

var viewer = new Cesium.Viewer('cesiumContainer');
viewer.camera.viewBoundingSphere({"center":{"x":1215020.301129722,"y":-4736341.9686844405,"z":4081630.311150717},"radius":200.90026973524507}, new Cesium.HeadingPitchRange(0, -2.0, 0));
viewer.camera.lookAtTransform(Cesium.Matrix4.IDENTITY);
@lilleyse
Copy link
Contributor

lilleyse commented Aug 2, 2016

One thing to try is turning RequestScheduler.prioritize to false or RequestScheduler.throttle to false.

@pjcozzi
Copy link
Contributor

pjcozzi commented Aug 10, 2016

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.

@lilleyse
Copy link
Contributor

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 RequestScheduler.prioritize is false?

@lilleyse
Copy link
Contributor

Either way I will look more into this.

@mramato
Copy link
Contributor Author

mramato commented Aug 10, 2016

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.

@pjcozzi
Copy link
Contributor

pjcozzi commented Aug 10, 2016

Clean cache or just use dev tools to throttle the speed.

The cache was warm and still noticeable for me.

@mramato
Copy link
Contributor Author

mramato commented Aug 26, 2016

Turns out this is also a problem in master too and is directly related to fog being disabled and has nothing to do with 3D Tiles.

I guess the bigger question is by is disabling fog producing such poor performance for a straight down close up view?

@mramato
Copy link
Contributor Author

mramato commented Aug 26, 2016

Add viewer.scene.fog.enabled = false; to my "working" example in the original post and you can see htis for yourself.

@pjcozzi
Copy link
Contributor

pjcozzi commented Aug 26, 2016

@bagnell can you please look at this when you have time? Ideally before 1.25 next Thursday.

@pjcozzi
Copy link
Contributor

pjcozzi commented Dec 20, 2016

Perhaps now duplicate with #4359.

@pjcozzi pjcozzi removed the bug bash label Jan 2, 2017
@mramato
Copy link
Contributor Author

mramato commented Jan 3, 2017

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.

@ggetz ggetz changed the title 3D Tiles demo has terrible imagery performance in IE 3D Tiles demo has terrible imagery performance Jan 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants