Updated AWS S3 Storage (markdown)

mikeprimm 2022-02-23 21:27:52 -06:00
parent 434dc0061f
commit e175d021a2

@ -55,7 +55,7 @@ Be sure to check the checkbox to grant the user this policy.
6. The following additional settings changes should also be done:
* Uncomment the JsonFileClientUpdateComponent section, and comment or delete the InternalClientUpdateComponent. Also, set **allowwebchat** to **false** (it is unsupported), and it is suggested to set **writeinterval** to 15 (or higher) - this will reduce how often chat, player positions, and other data are written to the S3 bucket (which can reduce API call charges (below)).
* Uncomment the JsonFileClientUpdateComponent section, and comment or delete the InternalClientUpdateComponent. Also, set **allowwebchat** to **false** (it is unsupported), and it is suggested to set **writeinterval** to 15 (or higher) AND to set the **updaterate** setting to 1000 times the same value - this will reduce how often chat, player positions, and other data are written to the S3 bucket (which can reduce API call charges (below)), and how often web users' browsers will poll the bucket for those updates.
<img width="815" alt="Screen Shot 2022-02-23 at 8 25 35 PM" src="https://user-images.githubusercontent.com/654487/155445528-03d3e975-dabd-446c-a434-d8cac17feafa.png">
* It is strongly suggested that the new **defaulttilescale** setting be used to reduce the number of tiles posted to S3, while increasing the size of the tiles (a setting of *2* is recommended). This will reduce the number of GET calls needed by the users to load the tiles on their screen, while still generating about the same bandwidth. It is also suggested to use the default **image-format** setting (jpg-q90) or the webp format, in order to minimize file sizes (png is NOT recommended, as this results in significantly larger files, and associated storage and bandwidth costs).