|
80 | 80 | { |
81 | 81 | "cell_type": "markdown", |
82 | 82 | "source": [ |
83 | | - "### Data Processing (Subsequent Runs)" |
84 | | - ], |
85 | | - "metadata": { |
86 | | - "collapsed": false |
87 | | - } |
88 | | - }, |
89 | | - { |
90 | | - "cell_type": "markdown", |
91 | | - "source": [ |
92 | | - "| Visualization Method / Grid Resolution | 30km | 15km | 7.5km | 3.75km |\n", |
93 | | - "|-----------------------------------------|-------------|-------------|-------------|--------------|\n", |
94 | | - "| Polygon Raster (Including Antimeridian) | 0 | 0 | 0 | 0 |\n", |
95 | | - "| Polygon Raster (Excluding Antimeridian) | 0.30 (0.00) | 1.02 (0.36) | 3.46 (0.01) | 13.60 (0.08) |\n", |
96 | | - "| Point Raster | 0.13 (0.03) | 0.16 (0.01) | 0.35 (0.00) | 1.08 (0.07) |" |
| 83 | + "We can see that Point Rasters are the best in terms of performance, about 86 times faster than Polygon Rasters (excluding AM). \n", |
| 84 | + "\n", |
| 85 | + "Both polygon plots scale linearly with an increase in resolution. A doubling in resolution leads to about a 4x increase in the number of polygons (a.k.a polygons), which is observed in the timings.\n", |
| 86 | + "\n", |
| 87 | + "Including antimeridian polygons leads to about a 20x slowdown across all resolutions, so it's suggested to keep `exclude_antimeridian=True` when working with larger datasets." |
97 | 88 | ], |
98 | 89 | "metadata": { |
99 | 90 | "collapsed": false |
|
102 | 93 | { |
103 | 94 | "cell_type": "markdown", |
104 | 95 | "source": [ |
105 | | - "### Visualization " |
| 96 | + "### Data Processing (Subsequent Runs)" |
106 | 97 | ], |
107 | 98 | "metadata": { |
108 | 99 | "collapsed": false |
|
111 | 102 | { |
112 | 103 | "cell_type": "markdown", |
113 | 104 | "source": [ |
114 | | - "| Visualization Method / Grid Resolution | 30km | 15km | 7.5km | 3.75km |\n", |
115 | | - "|----------------------------------------|------|------|-------|--------|\n", |
116 | | - "| Polygon Raster (0.5 Pixel Ratio) | 0 | 0 | 0 | 0 |\n", |
117 | | - "| Polygon Raster (1.0 Pixel Ratio) | 0 | 0 | 0 | 0 |\n", |
118 | | - "| Polygon Raster (4.0 Pixel Ratio) | 0 | 0 | 0 | 0 |\n", |
119 | | - "| Point Raster (0.5 Pixel Ratio) | 0 | 0 | 0 | 0 |\n", |
120 | | - "| Point Raster (1.0 Pixel Ratio) | 0 | 0 | 0 | 0 |\n", |
121 | | - "| Point Raster (4.0 Pixel Ratio) | 0 | 0 | 0 | 0 |" |
| 105 | + "| Visualization Method / Grid Resolution | 30km | 15km | 7.5km | 3.75km |\n", |
| 106 | + "|-----------------------------------------|-------------|-------------|-------------|--------------|\n", |
| 107 | + "| Polygon Raster (Including Antimeridian) | 0.31 (0.00) | 1.32 (0.31) | 3.85 (0.06) | 14.36 (0.13) |\n", |
| 108 | + "| Polygon Raster (Excluding Antimeridian) | 0.30 (0.00) | 1.02 (0.36) | 3.46 (0.01) | 13.60 (0.08) |\n", |
| 109 | + "| Point Raster | 0.13 (0.03) | 0.16 (0.01) | 0.35 (0.00) | 1.08 (0.07) |\n", |
| 110 | + "\n", |
| 111 | + "For subsequent runs (i.e. we have already run one plotting instance, which computes and caches the necessary data structures), performance for both Polygon methods is essentially identical.\n", |
| 112 | + "\n", |
| 113 | + "There is no caching currently implemented for Point Rasters, so the performance for each run is consistent with the initial run.\n" |
122 | 114 | ], |
123 | 115 | "metadata": { |
124 | 116 | "collapsed": false |
|
0 commit comments