On 15/09/11 15:03, Mikhail Sogrin wrote:
Hi Andy,
While the files show as 200MB that are sparse files. Linux will show 8M
files with "ls -l" but the directory, to "du -sh" is 208K. Sparse files
don't allocate all their space. OS/X seems to be difefrent - "du -sh"
reports the sum of the file sizes, but they are still sparse files and don't
consume all their disk space.
Good to know that they are sparse files and not taking much space on disk.
But they still require space when backing up, zipping, copying to other
machines, etc.
In theory, the index segment size is configurable (see
SystemTDB.SegmentSize) but it isn't tested for in the test suite.
That would require recompilation, as the parameter is final and cannot be
changed with original jars.
Yes - it needs a rebuild. It must not change during a run - complete
and utter chaos will result!
Different runs over the same data will work -- the Block size is the
unit of access, and segments is the mapping grouping only. This is way
direct mode and mapped mode can use the same database (at different times).
Andy
Kind regards,
Mikhail
