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

sci-wms performance #14

Open
rsignell-usgs opened this issue Nov 27, 2016 · 4 comments
Open

sci-wms performance #14

rsignell-usgs opened this issue Nov 27, 2016 · 4 comments

Comments

@rsignell-usgs
Copy link
Member

rsignell-usgs commented Nov 27, 2016

This request for a single tile from the SMAST NECOFS model takes about 2 minutes (!), when the ncWMS service is running on whoi.edu/gamone and accessing data via opendap from smast.umassd.edu:
http://gamone.whoi.edu/wms/datasets/necofs_massbay?service=WMS&request=GetMap&version=1.1.1&layers=u,v&styles=vectors_cubehelix&format=image/png&transparent=true&height=256&width=256&colorscalerange=0.0,1.0&numcontours=20&logscale=false&srs=EPSG:3857&vectorscale=20&bbox=-7856503.515263555,5087648.602661332,-7846719.575643052,5097432.5422818335
to produce this tile:

necofs_massbay

@kwilcox
Copy link

kwilcox commented Nov 27, 2016

Are scalar layers quicker?

@rsignell-usgs
Copy link
Member Author

Wow, that's like 1 second or less, right?
Why the huge difference?

@kwilcox
Copy link

kwilcox commented Nov 28, 2016

Filledcontours does not draw every cell... the vector request is actually drawing every cell's vectors that is in view. It's also processing 2x the data, but I'm assuming the slowdown is the matplotlib drawing. A small zoomed in area should be quick.

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

2 participants