.
Best regards,
Ivan
[1] - These names were mixed on purpose ;)
> ---Original Message---
> From: Jason Birch <[EMAIL PROTECTED]>
> Subject: RE: [OSGeo-Discuss] Raster data on RDBMS
> Sent: Oct 29 '08 15:09
>
> I find this stuff fascinating, but I
Ascent Inc.
From: [EMAIL PROTECTED] on behalf of G. Allegri
Sent: Wed 10/29/2008 12:50 PM
To: OSGeo Discussions
Subject: Re: [OSGeo-Discuss] Raster data on RDBMS
Thanks everyone for this interesting thread. I think the two
approaches have different goals:
- rendering-on-demand
Frank,
> My point is that a tile caching approach is really comparing tile caching
> performance to rendering-on-demand performance while I think the original
> point was that rendering-from-database and rendering-from-filesystem could
> have similar performance for input raster data.
D'accor
Thanks everyone for this interesting thread. I think the two
approaches have different goals:
- rendering-on-demand performance comparison
- raster serving performance comparison
Both are of interest, but they shouldn't be confused.
It might be helpful to write a wiki page (or something else) w
Sylvan Ascent Inc. wrote:
I think, that since the goal of all this storage of pyramids and the like is
just to get speed, that they aren't apples/oranges, but apples apples, since
they are both pyramid schemes, just in different places, either in front, or
in back of the server.
Roger,
My poin
CTED] <mailto:[EMAIL PROTECTED]>
www.sylvanascent.com <http://www.sylvanascent.com/>
www.topodepot.com <http://www.topodepot.com/>
From: [EMAIL PROTECTED] on behalf of Frank Warmerdam
Sent: Wed 10/29/2008 10:43 AM
To: OSGeo Discussions
Subject: Re: [OSGeo-Di
I find this stuff fascinating, but I believe that the Oracle EULA prohibits
users from disclosing the results of benchmark tests. Be careful how you
represent these results.
Jason
-Original Message-
From: Lucena, Ivan
Subject: [OSGeo-Discuss] Raster data on RDBMS
I would like to
Sylvan Ascent Inc. wrote:
Mike and Ivan,
I'd like to see them also compared to a caching solution, like GeoWebCache,
or TileCache. These effectively create a file-based "database" of little
bitty tiles at certain resolutions, kind of like a tile pyrimid that is
created gradually over time as the
Inc.
800-362-8971
+34 626 855 662
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
From: [EMAIL PROTECTED] on behalf of Smith, Michael ERDC-CRREL-NH
Sent: Wed 10/29/2008 10:13 AM
To: Lucena, Ivan; OSGeo Discussions; Paul Ramsey
Subject: Re: [OSGeo-Discuss] Ras
he the BLOB in
> memory. So the next time a user zoom-in the performance would be even better.
>
> I am trying to setup a mapserver experiment on that issue but for now I would
> like to keep my analysis on that very simple process of extracting a subset.
>
> Best regards,
>
of extracting a subset.
Best regards,
Ivan
> ---Original Message---
> From: Paul Ramsey <[EMAIL PROTECTED]>
> Subject: Re: [OSGeo-Discuss] Raster data on RDBMS
> Sent: Oct 29 '08 05:00
>
> The data is chunked in Oracle into tiles, so unless you tile
The data is chunked in Oracle into tiles, so unless you tile the TIFF
as well you aren't really doing a direct comparison. Even if you end
up with the same numbers for both processes, I'll still be impressed,
since I assumed Oracle would have a higher overhead.
P.
On Tue, Oct 28, 2008 at 9:54 PM,
Hi There,
I would like to return to a discussion that we had months ago about raster on
RDBMS. But this time I would like to present some number.
As long as I could recall there was basically two major arguments contrary to
storing raster on RDBMS. One very pragmatical: "Why waste precious proc
13 matches
Mail list logo
