256a259
< | m5.large | 7 GB | 680000 | 500000 |
< | r3.large | 15 GB | 1360000 | 1000000 |
< | r3.xlarge | 30.5 GB | 2720000 | 2000000 |
< | r3.2xlarge | 61 GB | 5450000 | 4000000 |
255d256
> | m5.xlarge | 16 GB | 1360000 | 1000000 |
> | m5.2xlarge | 32 GB | 2720000 | 2000000 |
> | m5.4xlarge | 64 GB | 5440000 | 4000000 |
> | m5.8xlarge | 128 GB | 10880000 | 8000000 |
253a253
< * Virtuoso always takes full advantage of the memory it's configured to use. This may be much less than is found in its host environment/AMI. This AMI is pre-configured for an <code>m5.large</code> EC2 Instance Type, so will use 7GB or RAM. If you choose a larger EC2 Instance Type, then the <code><nop>NumberOfBuffer</code> and <code><nop>MaxDirtyBuffers</code> parameters in the <code>/opt/virtuoso/database/virtuoso.ini</code> configuration file should be increased to correspond to the chosen Instance Type's available memory, as detailed in the [[http://virtuoso.openlinksw.com/dataspace/doc/dav/wiki/Main/VirtRDFPerformanceTuning#General%20Memory%20Usage%20Settings][Virtuoso Performance Tuning Guide]]. A few examples are shown below. After changing these or any other settings in the INI file, restart the Virtuoso server [[#Virtuoso%20Server][as described above]].
252d253
> * Virtuoso always takes full advantage of the memory it's configured to use. This may be much less than is found in its host environment/AMI. This AMI is pre-configured for an <code>m5.xlarge</code> EC2 Instance Type, so will use 16GB or RAM. If you choose a larger EC2 Instance Type, then the <code><nop>NumberOfBuffer</code> and <code><nop>MaxDirtyBuffers</code> parameters in the <code>/opt/virtuoso/database/virtuoso.ini</code> configuration file should be increased to correspond to the chosen Instance Type's available memory, as detailed in the [[http://virtuoso.openlinksw.com/dataspace/doc/dav/wiki/Main/VirtRDFPerformanceTuning#General%20Memory%20Usage%20Settings][Virtuoso Performance Tuning Guide]]. A few examples are shown below. After changing these or any other settings in the INI file, restart the Virtuoso server [[#Virtuoso%20Server][as described above]].
210a212
< <i><b>Note 1:</b> The <code><nowiki>update_ontology.sh</nowiki></code> script is written to use the default <code>dba</code> password that is derived from the AMI <code>instance-id</code>. Thus, if you have changed that password as recommended, you will need to update the script with the same password.</i>
< %BR%%BR%
< <i><b>Note 2:</b> The first time these change-sets are applied to your instance, it may take several hours or even days, depending on server resources and bandwidth, for all the change-sets to be loaded, and so for the DBpedia instance to be brought up to date and subsequently to obtain realtime updates from Wikipedia. You can monitor the <code>Latest changes</code> and <code>Top 20 Most Recently Updated Entities</code> sections of the live update web page (<code>http://{amazon-ec2-ami-dns-name-or-ip-address}/live</code>) to see the current state of the live update process.</i>
209d212
> <i><b>Note:</b> The first time these change-sets are applied to your instance, it may take several hours or even days, depending on server resources and bandwidth, for all the change-sets to be loaded, and so for the DBpedia instance to be brought up to date and subsequently to obtain realtime updates from Wikipedia. You can monitor the <code>Latest changes</code> and <code>Top 20 Most Recently Updated Entities</code> sections of the live update web page (<code>http://{amazon-ec2-ami-dns-name-or-ip-address}/live</code>) to see the current state of the live update process.</i>
203d204
> 1 Edit the file <code><nowiki>dbpedia_updates_downloader.ini</nowiki></code> and set the <code>Store.pw</code> param to the <cod>dba</code> users password which by default will be set to the AMI <code>instance-id</code>, unless it has already been changed. Thus, if you have changed that password as recommended, you will need to update the script with the same password.</i>
> %BR%%BR%
199a199
<
198d199
>
34a34
< 1 Choose a suitable size <b>EC2 Instance Type</b> and License <b>Quantity</b>, then click on the button <b>Continue to Configuration</b> button.
33d34
> 1 Choose a suitable size <b>EC2 Instance Type</b> and License <b>Quantity</b>, then click on the button <b>Continue to Configuration</b> button. An <b>EC2 Instance Type</b> with a minimum of 16GB RAM is recommended, <code>m5.xlarge</code> for example.