Jerry, I'm not sure I follow your issue. Mapcache itself won't hit your source data, it will only be accessed through by the configured wms server if a tile was not found in the local cache. The seeder will only hit the wms if a given tile was not present in the cache (or if you have passed --force on the command line)
-- thomas On 23 April 2014 21:33, jrumbolt <[email protected]> wrote: > Hi, > > I have my source datasets on Amazon S3 and mounted with s3fs. There is a > fair amount of latency in any check/read in the mounted s3 bucket to I use > the mapcache_seed to fill a cache on the local system in a one time > operation. > > I'm finding that mapcache seems to want to check the source data before > hitting the cache and it's slow, high latency, even though the cache is > local and ready. > > Is there some option that I can set that will have mapcache get from the > cache first before trying to do anything with the source data? > > Regards, > > Jerry > > > > -- > View this message in context: > http://osgeo-org.1560.x6.nabble.com/mapcache-check-cache-before-testing-source-data-tp5136792.html > Sent from the Mapserver - User mailing list archive at Nabble.com. > _______________________________________________ > mapserver-users mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/mapserver-users _______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
