I have implemented a tile server. But I haven't build any tile cache yet. For the very first time when I open a tile in browser, it took around 53seconds to load for a single tile(256*256, zoom level 1, openstreetmap carto style ). My question is - **Is this time taken normal? or Should I look into my Postgres configuration to further minimize the time. And Is that there any minimum time for tile loading(without any prerender or cache) that can be achieved using postgres tuning?**

I have implemented a tile server. But I haven't build any tile cache yet. For the very first time when I open a tile in browser, it took around 53seconds to load for a single tile(256*256, zoom level 1, openstreetcarto openstreetmap carto style ). My question is - **Is this time taken normal? or Should I look into my Postgres configuration to further minimize the time. And Is that minimum time for tile loading(without any prerender or cache) that can be achieved using postgres tuning?**

I have implemented a tile server. But I haven't build any tile cache yet. For the very first time when I open a tile in browser, it took around 53seconds to load for a single tile(256*256). tile(256*256, zoom level 1, openstreetcarto style ). My question is - **Is this time taken normal? or Should I look into my Postgres configuration to further minimize the time. And Is that minimum time for tile loading(without any prerender or cache) that can be achieved using postgres tuning?**

I have implemented a tile server. But I haven't build any tile cache yet. For the very first time when I open a tile in browser, it took around 53seconds to load for a single tile(256*256). My question is - **Is this time taken normal? or Should I look into my Postgres configuration to further minimize the time. And Is that minimum time for tile loading(without any prerender or cache) that can be achieved using postgres tuning?**