[ncl-talk] Slow draw() debugging/profiling

[Mary Haley]

Hi Matthew,

There are a number of issues that can help with speeding up your script. We
do have a profiling tool, but it only profiles the NCL code itself. I
believe it would show you what you already know, and that is the "draw"
command is taking a long time.

You didn't say what kind of plots you are creating, but if you are creating
filled contour plots, then usually the single best thing you can do to
speed things up is to set the resource:

res at cnFillMode = "RasterFill"

which will cause NCL to use raster contouring instead of smooth contouring
which can be drastically slower for larger grids.

If this doesn't help, then please post back to ncl-talk with more
information about what kind of plot you are creating, how big your data
array(s) are, and what graphical resources you are setting.

--Mary


On Sun, Jun 26, 2016 at 7:39 PM, Matthew Scutter <yellowplantain at gmail.com>
wrote:

> Hi ncl-talk,
> I have a number of plots which are taking many minutes in the draw() call.
> Is there some way I can expose some more debugging output to determine why?
> Or better yet, profile it?
> I am plotting large plots (>2048x2048).
>
> _______________________________________________
> ncl-talk mailing list
> ncl-talk at ucar.edu
> List instructions, subscriber options, unsubscribe:
> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ucar.edu/pipermail/ncl-talk/attachments/20160627/41f05022/attachment.html