[Tilesathome] Cutover to new server? When?

[spaetz]

On Sat, Jul 12, 2008 at 11:21:55AM -0700, Alan Millar wrote:

> I'll see if I can come up with some patches to address the new issues.

Cool

> are just amazing.  I LOVE being able to upload a tile and see it within a
> minute.  I also like the debug log on the main page showing the most
> recent activity; that's cool!

Yes, quick turnaround time is one of the plusses for t at h, at least that is how it is supposed to be. Glad you like the log file excerpt too :-).
 
> I personally like the fallback approach.  If it takes 120 seconds to build
> a tileset that completely matches the current system, it seems like it
> will take longer than that for a client to re-render and upload it.

120 seconds with no optimized blankness lookup at all (e.g. I spawn a new mysql command line client for each lookup). I bet that could be optimized a lot, given some effort.
 
> What are your thoughts or plans for the 13 million z12 blank sea tiles?

Short term: Nothing. just build up lots of 5700 byte long tilesetfiles stating that this is a blank z12. This is the fastest solution, but will waste disk space. We are currently not short of disk space and we will waste a lot anyway as long as we have to keep the legacy tiles around.

Long term: Use a blankness database that is only used for completely blank z12 tiles or above (recursive lookups). Move all blank tilesetfiles into the blankness db. Given that the only benefit is saved disk space, this is not extremly top on my list though.