| 95 | |
| 96 | |
| 97 | = Tile cache = |
| 98 | |
| 99 | 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. |
| 100 | |
| 101 | '''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. |
| 102 | |
| 103 | The cache can be enabled in rasmgr.conf by specifying a `--cachelimit` parameter after the `-xp` parameter: |
| 104 | {{{ |
| 105 | --cachelimit <limit> (default: 0) |
| 106 | specifies upper limit in bytes on using memory for caching |
| 107 | }}} |
| 108 | |
| 109 | An example `rasmgr.conf` configuration that allows the cache to use up to 1GB memory: |
| 110 | {{{ |
| 111 | define dbh rasdaman_host -connect RASBASE |
| 112 | define db RASBASE -dbh rasdaman_host |
| 113 | |
| 114 | define srv N1 -host HOST -type n -port 9000 -dbh rasdaman_host |
| 115 | change srv N1 -countdown 20000000 -autorestart on -xp --timeout 30000000 --cachelimit 1073741824 |
| 116 | }}} |