[MapProxy] Jpeg Encoding Performance

[Oliver Tonnhofer]

Hi,

encoding a JPEG tile should take a few ms at most. Can you provide a minimal working configuration? Can you provide the output from mapproxy-util serve-develop, including lines with mapproxy.source.request?

Regards,
Oliver

-- 
Oliver Tonnhofer  | Omniscale GmbH & Co KG  | https://omniscale.com
OpenStreetMap WMS and tile services         | https://maps.omniscale.com





> On 15.06.2017, at 07:44, Ryan How <ryan at bitworks.com.au> wrote:
> 
> Hi Everyone,
> 
> I'm enjoying using MapProxy and it is working well for our use case.
> 
> I've been attempting to use the mixed format cache to decrease the download size of the tiles for end clients. However I have found that the JPEG encoding performance seems to be very slow. It takes around 8 seconds to retrieve a tile, opposed to the 200ms if it is in PNG. (The source is in PNG).
> 
> I also seem to have this issue if I am combining 2 layers and outputting in JPEG format.
> 
> The server has a fast CPU and plenty of memory and is running through apache with mod_wsgi.
> 
> Is this just the type of performance that is expected if any re-encoding needs to take place? And therefore it would be expected to perform this while seeding, rather than on-the-fly when serving to clients?
> 
> 
> 
> Thanks, Ryan
> 
> 
> 
> _______________________________________________
> MapProxy mailing list
> MapProxy at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapproxy