Ticket #5 (new defect)

Opened 11 months ago

Last modified 8 months ago

Depth first seeding

Reported by: cholmes Owned by: arneke
Priority: major Milestone: 1.1
Component: core Version:
Keywords: Cc:

Description

With large datasets it makes sense to do some smart depth first seeds, since you'll likely be requesting the same feature over and over again as you go through the different zoom levels of a single area.

On the GeoServer side we could do some optimizations to do a cache of features that would play well with these kinds of requests, so that most data would only have to be read from disk once, and then would be held in memory for subsequent requests. But we may get some benefits just from caching at the operating system and database levels even without doing anything in GeoServer, since it'll be requesting the same disk blocks, ect.

Change History

Changed 8 months ago by arneke

These are very abstract requirements, maybe more suitable for a developer mailinglist discussion than a ticket ?

Changed 8 months ago by arneke

Ignore my comment, was meant for ticket #33

Note: See TracTickets for help on using tickets.