Changes between Version 15 and Version 16 of Performance

Timestamp:

Aug 7, 2013, 3:42:16 PM (11 years ago)

Author:

Dimitar Misev

Comment:

—

Performance

@@ -174 +174 @@
 }}}
 
-To make most optimal use of the tile cache feature, it's important to understand how it works. The tile cache especially helps with regular tiling, when there are many partial updates at slices along some axis. The [wiki:Tiling#Caveat regular tiling] section provides an introduction into this, here we continue with the same example from that section and define a ''best practice'' for using the tile cache.
+To make most optimal use of the tile cache feature, it's important to understand how it works. The tile cache especially helps with regular tiling, when there are many partial updates at slices along some axis. The [wiki:Tiling#Caveat regular tiling] section provides an introduction into this (_please read before continuing_), here we continue with the same example from that section and define a ''best practice'' for using the tile cache.
 
 As we has been demonstrated by the regular tiling example, inserting a 1000x1000x1 data cube results in generating a 1000x1000x1000 cube, due to the specific tiling scheme used. If the tile cache is enabled and at least 1000x1000x1000 = 1GB of memory is allowed with `--cachelimit`, this cube will fit in memory and will be cached. If less memory is allowed for the tile cache, then some of the 100x100x1000 tiles that don't fit in the memory will have to be written to disk. Assuming that the whole cube fits in main memory, then any slices updating the cube along the third dimension will be very fast, e.g.