Dear Mika, Dear Christopher,
thank you again, these informations are really new for me. >In general, the latter is based entirely on the type of features: there >is usually not a *significant* difference i parsing time between >different formats of vector serialization once you've whittled >the result set down to the IE6/IE7 limit of ~100 features. I understand right, more then 100 features at a time provocate a delay? 100 features is not sooooo much..... >Perhaps, we will come up with more concrete ideas after you have also >brougth about something more concrete. In the moment I use a Mapbender-lot: http://www.gastronomap.de/mapbender25/frames/login.php?&gui_id=gastronomap&name=gastronomap&password=gastronomap&mb_myBBOX=3435722.5,5792615.5,3435922.75,5792816 If you zoom out, you can see there are about 500 elements (in a wms) at a time, thats what I want to integrate in Open Layers in a performant way. >Once you've optimized the server side, investigating different options >on the client side should be relatively simple, but pick one at a time >and optimize. Can you give me a hint please? What kinds of options are these at the client side? Thank you again for your help, Best regards, Kai -------- Original-Nachricht -------- > Datum: Thu, 5 Feb 2009 08:51:14 -0500 > Von: Christopher Schmidt <[email protected]> > An: Kai Behncke <[email protected]> > CC: Mika Lehtonen <[email protected]>, [email protected] > Betreff: Re: [OpenLayers-Users] Performance of own (vector) data in Open > Layers > On Thu, Feb 05, 2009 at 02:24:43PM +0100, Kai Behncke wrote: > > Dear Mika, > > > > well "my server " is a normal root server in the Internet. > > "My data" in that case are Vector-Point-Data, I have them in a > PostGIS-Database or can have them as a "typical" shape-file. > > I`m quite new to Open Layers and definetely quite impressed. > > > > I wonder in general now which way might be the most performant way to > show "own" geodata (in Combination with the > google-api-layer,osm-api-ayer,virtual earth-api-layer) to the public in Open > Layers. > > > > But, well, I will test beside from that question also how to improve the > speed of the WFS, I`m pretty sure there will be some possibilities > (indizes and so on). > > It seems you are trying to address multiple performance concerns at the > same time. > * Server side: the time it takes to return a set of features in > response to a query > * Client side: How long it takes to parse and draw them. > > In general, the latter is based entirely on the type of features: there > is usually not a *significant* difference i parsing time between > different formats of vector serialization once you've whittled > the result set down to the IE6/IE7 limit of ~100 features. > Once you've optimized the server side, investigating different options > on the client side should be relatively simple, but pick one at a time > and optimize. > > Regards, > -- > Christopher Schmidt > MetaCarta -- Jetzt 1 Monat kostenlos! GMX FreeDSL - Telefonanschluss + DSL für nur 17,95 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a _______________________________________________ Users mailing list [email protected] http://openlayers.org/mailman/listinfo/users
