Changes between Version 7 and Version 8 of Performance

Timestamp:

Jun 16, 2013, 9:53:38 PM (11 years ago)

Author:

Dimitar Misev

Comment:

—

Performance

@@ -24 +24 @@
 || 0:31,0:31,0:149 || 460800 || 35 minutes || 184M || '''19416M''' || 267 MB || 18 GB ||
 
- * Using [#TileCache tile cache]
+ * Using [#Tilecache tile cache]
    
 || '''Tiling scheme''' || '''Tile size''' || '''Import time''' || '''DB size before''' || '''DB size after''' || '''BLOBs size''' || '''BLOBs size2''' ||
@@ -104 +104 @@
 A tile cache can be enabled in rasdaman during bulk ingestion, in order to work around inefficiencies of BLOB handling in postgres and slow performance for certain tiling schemes.
 
-'''IMPORTANT:''' At the moment the tile cache should be used during bulk ingestion '''_ONLY_''', and disabled afterwards. Leaving the tile cache on will cause selection queries to fail randomly. Furthermore, it is best to have only one server defined in rasmgr.conf, and `-countdown` and `--timeout` parameters set to very large values.
+== How to use ==
 
 The cache can be enabled in rasmgr.conf by specifying a `--cachelimit` parameter after the `-xp` parameter:
@@ -120 +120 @@
 change srv N1 -countdown 20000000 -autorestart on -xp --timeout 30000000 --cachelimit 1073741824
 }}}
+
+When enabled, `INSERT` and `UPDATE` rasql statements can be issued in the normal way. At the end of the ingestion a `COMMIT` command should be executed, to make sure that the cache is cleared and everything is flushed to disk. E.g.
+{{{
+rasql -q 'insert into coll ...'
+rasql -q 'update coll ...'
+rasql -q 'update coll ...'
+rasql -q 'update coll ...'
+
+# done with ingestion
+rasql -q 'commit'
+}}}
+
+== Important limitation ==
+
+At the moment the tile cache should be used during bulk ingestion '''_ONLY_''', and disabled afterwards. Leaving the tile cache on will cause selection queries to fail randomly. Furthermore, it is best to have only one server defined in rasmgr.conf, and `-countdown` and `--timeout` parameters set to very large values.