If the problem is what we have been assuming, I see where Martin's algorithm
could be applied:
com.vividsolutions.jump.workbench.ui.renderer.style.StyleUtil#toShape()
We could do a conversion of large linestrings whose bounding boxes contain
the viewport, to "rough clip" MultiLineStrings instead of the clipGeometry
call. This should enable Java's graphics clipper to do its work
efficiently. The tough part is to not slow down the best case performance
too much.
Larry
On Mon, Feb 22, 2010 at 4:44 PM, Martin Davis <mbda...@refractions.net>wrote:
> Yeah, it seems to me that I haven't seen much speed impact from
> rendering fairly large linestrings. I suppose it's possible that if the
> linestring was really complex the intersection() computation might be
> slow, however.
>
> In any case, computing a full intersection() is definitely doing more
> work than required for rendering. So this would be a good thing to
> optimize. It's one of those things which isn't necessarily all that
> noticeable, but is quietly burning cycles all the time.
>
> Larry Becker wrote:
> > Better send it to me too. All the cases I've found in the wild render
> very
> > quickly. See the attached for an example.
> >
> > Larry
> >
> > On Mon, Feb 22, 2010 at 4:13 PM, Martin Davis <mbda...@refractions.net
> >wrote:
> >
> >
> >> Stefan, for future reference can you send the linestring, and the
> >> viewport which causes the problem?
> >>
> >> Stefan Steiniger wrote:
> >>
> >>> mhm.. ok, so I would guess the problem is related to the size of the
> >>> geometries and its drawing?
> >>> I recently had a problem - drawing a linestring that consisted of more
> >>> than 1000 points. I couldn't do anything for 20-30 seconds on MS Vista,
> >>> my XP was a bit faster. However, the problem solved when I connected
> the
> >>> 1000 points with linestrings that have only a start and endpoint, i.e.
> >>> instead of drawing 1 linestring a had to draw now 500, but here the 500
> >>> lines could be drawn one after each other, and everything is done
> within
> >>> 2-3 seconds (instead of 20 secs)
> >>>
> >>> (if Larry wants to test, I can send that linestring?)
> >>>
> >>> however, I am not sure why working with the 1000 points linestring is
> so
> >>> slow (i.e. does paint make some tests?)
> >>>
> >>> stefan
> >>>
> >>> luca marletta wrote:
> >>>
> >>>
> >>>> luca marletta
> >>>> www.beopen.it
> >>>>
> >>>>
> >>>>
> >>>> On Fri, Feb 19, 2010 at 5:42 PM, Larry Becker <becker.la...@gmail.com
> >
> >>>>
> >> wrote:
> >>
> >>>>> Hi luca,
> >>>>>
> >>>>> When you try to select features, does the status bar quickly show
> >>>>>
> >> your
> >>
> >>>>> selection count, even though no selection handles appear?
> >>>>>
> >>>>> If not, this explains why the right click menu is not appearing.
> It
> >>>>>
> >> needs
> >>
> >>>>> selection information to enable or disable options.
> >>>>>
> >>>>>
> >>>> Larry, no I had not much problem with showing selection count, is
> anyway
> >>>>
> >> quick.
> >>
> >>>> I noticed an important stuff.
> >>>>
> >>>> May dataset is full of large and aggregated geometry and in this case
> >>>> I guess geometry index can not much help.
> >>>>
> >>>> If I explode all, I reduce the delay a lot.
> >>>>
> >>>> luca
> >>>>
> >>>>
> >>>>
> >>
> ------------------------------------------------------------------------------
> >>
> >>>> Download Intel® Parallel Studio Eval
> >>>> Try the new software tools for yourself. Speed compiling, find bugs
> >>>> proactively, and fine-tune applications for parallel performance.
> >>>> See why Intel Parallel Studio got high marks during beta.
> >>>> http://p.sf.net/sfu/intel-sw-dev
> >>>> _______________________________________________
> >>>> Jump-pilot-devel mailing list
> >>>> Jump-pilot-devel@lists.sourceforge.net
> >>>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
> >>>>
> >>>>
> >>>
> >>
> ------------------------------------------------------------------------------
> >>
> >>> Download Intel® Parallel Studio Eval
> >>> Try the new software tools for yourself. Speed compiling, find bugs
> >>> proactively, and fine-tune applications for parallel performance.
> >>> See why Intel Parallel Studio got high marks during beta.
> >>> http://p.sf.net/sfu/intel-sw-dev
> >>> _______________________________________________
> >>> Jump-pilot-devel mailing list
> >>> Jump-pilot-devel@lists.sourceforge.net
> >>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
> >>>
> >>>
> >>>
> >> --
> >> Martin Davis
> >> Senior Technical Architect
> >> Refractions Research, Inc.
> >> (250) 383-3022
> >>
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> Download Intel® Parallel Studio Eval
> >> Try the new software tools for yourself. Speed compiling, find bugs
> >> proactively, and fine-tune applications for parallel performance.
> >> See why Intel Parallel Studio got high marks during beta.
> >> http://p.sf.net/sfu/intel-sw-dev
> >> _______________________________________________
> >> Jump-pilot-devel mailing list
> >> Jump-pilot-devel@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
> >>
> >>
> >
> >
> >
> >
> >
> > ------------------------------------------------------------------------
> >
> > ------------------------------------------------------------------------
> >
> >
> ------------------------------------------------------------------------------
> > Download Intel® Parallel Studio Eval
> > Try the new software tools for yourself. Speed compiling, find bugs
> > proactively, and fine-tune applications for parallel performance.
> > See why Intel Parallel Studio got high marks during beta.
> > http://p.sf.net/sfu/intel-sw-dev
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Jump-pilot-devel mailing list
> > Jump-pilot-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
> >
>
> --
> Martin Davis
> Senior Technical Architect
> Refractions Research, Inc.
> (250) 383-3022
>
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Jump-pilot-devel mailing list
> Jump-pilot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>
--
Larry Becker
Integrated Systems Analysts, Inc.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
