Update README.md
This commit is contained in:
parent
5b130598c5
commit
e8704c2cb9
19
README.md
19
README.md
|
@ -39,15 +39,24 @@ Chunk size can be adjusted easily via configuration file.</li>
|
||||||
<b>Remarks:</b>
|
<b>Remarks:</b>
|
||||||
<ul>
|
<ul>
|
||||||
<li> config.json contains brief description of each configuration parameter</li>
|
<li> config.json contains brief description of each configuration parameter</li>
|
||||||
<li>Make sure, that username, you use in your PostgreSQL connection details, defined as superuser (usually "postgres")<br> More info: <a href="http://www.postgresql.org/docs/current/static/app-createuser.html">http://www.postgresql.org/docs/current/static/app-createuser.html</a></li>
|
<li>Make sure, that username, you use in your PostgreSQL connection details, defined as superuser (usually "postgres")<br> More info: <a href="http://www.postgresql.org/docs/current/static/app-createuser.html">http://www.postgresql.org/docs/current/static/app-createuser.html</a></li>
|
||||||
</ul>
|
</ul>
|
||||||
|
|
||||||
<p><b>4.</b> Go to nmig directory, install dependencies, and run the app.<br />
|
<p><b>4.</b> Go to nmig directory, install dependencies, and run the app with <code>--expose-gc</code> flag<br />
|
||||||
<b>Sample:</b><br />
|
<b>Sample:</b><br />
|
||||||
<pre>$ cd /path/to/nmig</pre><br />
|
<pre>$ cd /path/to/nmig</pre><br />
|
||||||
<pre>$ npm install</pre><br />
|
<pre>$ npm install</pre><br />
|
||||||
<pre>$ node main.js</pre><br />
|
<pre>$ node --expose-gc main.js</pre><br />
|
||||||
</p>
|
</p>
|
||||||
|
<p>
|
||||||
|
|
||||||
|
<b>Remark</b>: you can increase node.js memory limit (RAM usage) using <code>--max-old-space-size</code> flag<br />
|
||||||
|
</p>
|
||||||
|
<p>
|
||||||
|
|
||||||
|
Following command will increase memory limit to ~2GB and run nmig
|
||||||
|
<br /> <code>$ node --max-old-space-size=2048 --expose-gc main.js</code>
|
||||||
|
</p>
|
||||||
|
|
||||||
<p><b>5.</b> At the end of migration check log files, if necessary.<br />
|
<p><b>5.</b> At the end of migration check log files, if necessary.<br />
|
||||||
Log files will be located under "logs_directory" folder in the root of the package.<br />
|
Log files will be located under "logs_directory" folder in the root of the package.<br />
|
||||||
|
@ -70,7 +79,7 @@ which includes data types mapping, creation of tables, constraints, indexes, <br
|
||||||
PKs, FKs, migration of data, garbage-collection (VACUUM) and analyzing the newly created <br />
|
PKs, FKs, migration of data, garbage-collection (VACUUM) and analyzing the newly created <br />
|
||||||
PostgreSQL database took 1 minute 18 seconds.</p>
|
PostgreSQL database took 1 minute 18 seconds.</p>
|
||||||
<p>
|
<p>
|
||||||
<b>Remark:</b> it is highly recommended to VACUUM newly created database! <br />
|
<b>Remark:</b> it is highly recommended to VACUUM newly created database! <br />
|
||||||
Just keep in mind, that VACUUM is a very time-consuming procedure. <br />
|
Just keep in mind, that VACUUM is a very time-consuming procedure. <br />
|
||||||
So if you are short in time - disable VACUUM via config.json ("no_vacuum" parameter). <br />
|
So if you are short in time - disable VACUUM via config.json ("no_vacuum" parameter). <br />
|
||||||
Such step will save you ~25% of migration time. <br />
|
Such step will save you ~25% of migration time. <br />
|
||||||
|
|
Loading…
Reference in a new issue