[mapguide-internals] MapGuide RFC 112 - sqlite based tile cache
traian.stanev at autodesk.com
Wed May 11 10:56:35 EDT 2011
"Generating tiles is currently done using a rather brute force approach, by storing tiles in a database, it can be queried for existing tiles and only missing tiles can be requested."
What do you mean by brute force? Doesn't tile existence checking come down to a file existence check?
"Using a sqlite database will use less disk space than a disk based tile cache."
Do you have some numbers about the expected improvement? Inside its file, SQLite is basically a file system which will exhibit incomplete page filling and overflow, similar to a regular file system.
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Zac Spitzer
Sent: Saturday, May 07, 2011 3:12 AM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] MapGuide RFC 112 - sqlite based tile cache
Solution Architect / Director
Ennoble Consultancy Australia
+61 405 847 168
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
More information about the mapguide-internals