Ignore:
Timestamp:
May 4, 2011, 8:42:36 PM (14 years ago)
Author:
rick
Message:

Alternative heatmap generation 'framework'. Simple/Single file with no
persistent storage, making debugging easy.

This proves that the heatmap code itself is not causing the issues, but the
image manipulation PIL is not so fast (or properly utilized). Might want to
consider a more advanced image generation toolkit. (2000 entries: 5+ secs).

Also loading a large dataset into Objects seems to be very slow. The database
call is effient (just a single one), but building all the related objects,
makes is slow (2000 entries: 1+ sec). Might want to check if raw queries suit
to avoid conversion our needs:

http://docs.djangoproject.com/en/dev/topics/db/sql/

File:
1 edited

Legend:

Unmodified
Added
Removed
  • TabularUnified src/django_gheat/website/static/OpenStreetMap.js

    r9139 r9147  
    154154    CLASS_NAME: "OpenLayers.Layer.Overlay1"
    155155});
     156
     157OpenLayers.Layer.OSM.Overlay2 = OpenLayers.Class(OpenLayers.Layer.OSM, {
     158    initialize: function(name, options) {
     159        var url = [
     160            "/website/tile/${z}/${x},${y}.png"
     161        ];
     162        options = OpenLayers.Util.extend({ numZoomLevels: 21 }, options);
     163        var newArguments = [name, url, options];
     164        OpenLayers.Layer.OSM.prototype.initialize.apply(this, newArguments);
     165    },
     166
     167    CLASS_NAME: "OpenLayers.Layer.Overlay2"
     168});
Note: See TracChangeset for help on using the changeset viewer.