<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel>
        <title>Net/FSE User Community - Installation</title>
        <description>This forum contains information on the installation and configuration of Net/FSE. Does not cover data type support (see Data Type Support forum).</description>
        <link>http://netfse.org/support/list.php?4</link>
        <lastBuildDate>Tue, 07 Sep 2010 08:02:23 -0500</lastBuildDate>
        <generator>Phorum 5.2.9a</generator>
        <item>
            <guid>http://netfse.org/support/read.php?4,19,19#msg-19</guid>
            <title>Managing Disk Space (no replies)</title>
            <link>http://netfse.org/support/read.php?4,19,19#msg-19</link>
            <description><![CDATA[ There are several key parameters that can help you conserve disk space in Net/FSE. All these features can be adjusted in the server config file located by default at /etc/netfse/VERSION/local.cnf. After making changes, restart of the server process is required. <br />
<br />
<b>AutoMigrate::max</b><br />
The default setting here is 50, indicating that at most 50 PostgreSQL tables should be used to store data per data type. Each table contains TempTableSize records. These tables are not optimized for storage size and can end up eating up a lot of disk if either value is very high. <br />
<br />
Consider reducing AutoMigrate::max to 25 to conserve disk. This will force the migration subsystem to kick in earlier and move data from PostgreSQL to flat file b+ trees, which can then be compressed as needed. There is a trade off however as results stored in the PostgreSQL tables are much faster to search than records in the flat file b+ tree indexing mechanism. <br />
<br />
Note that this setting should be larger than AutoMigrate::min (default is 3), which tells the system to keep a minimum number of PostgreSQL tables per type. <br />
<br />
<b>AutoMigrate::deletedays</b> (0.3 release only)<br />
This setting is set to -1 by default, indicating that the feature is off. If set to a positive integer, the system will delete data that is older than the number of days specified. This in effect makes the system function as a ring buffer, deleting older data over time. Currently this function only works universally for all data types and cannot be customized, for instance  to delete high volume data faster than low volume data.<br />
<br />
<b>AutoMigrate::days</b> <br />
This is set to 10 by default, indicating that the migration process should try to migrate data that is older than 10 days. This is a rather conservative setting and probably should not be reduced, as the performance benefits outweigh any small storage savings.]]></description>
            <dc:creator>BenUphoff</dc:creator>
            <category>Installation</category>
            <pubDate>Mon, 06 Sep 2010 14:11:38 -0500</pubDate>
        </item>
        <item>
            <guid>http://netfse.org/support/read.php?4,12,12#msg-12</guid>
            <title>How to avoid filesystem from filling up (2 replies)</title>
            <link>http://netfse.org/support/read.php?4,12,12#msg-12</link>
            <description><![CDATA[ Hi,<br />
<br />
Is there a configuration setting for Net/FSE that prevents from filesystem from being filled up? <br />
I am looking for a ring buffer type of functionality.<br />
If there is no way to do this, what can be done manually?<br />
<br />
Thanks in advance.]]></description>
            <dc:creator>mnejat</dc:creator>
            <category>Installation</category>
            <pubDate>Mon, 06 Sep 2010 14:12:57 -0500</pubDate>
        </item>
    </channel>
</rss>
