# Tsi1 option in InfluxDB 1.7.8

**URL:** <https://community.influxdata.com/t/tsi1-option-in-influxdb-1-7-8/22487>\
**Category:** InfluxDB 1\
**Created:** [November 11, 2021, 8:33am UTC](https://community.influxdata.com/t/tsi1-option-in-influxdb-1-7-8/22487 "2021-11-11T08:33:50Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![zhongming\_ZHAO](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/zhongming_zhao/32/8720_2.png) [@zhongming\_ZHAO](https://community.influxdata.com/u/zhongming_ZHAO)\
**Post date:** [November 11, 2021, 8:33am UTC](https://community.influxdata.com/t/tsi1-option-in-influxdb-1-7-8/22487/1 "2021-11-11T08:33:50Z")

</div>

We are running InfluxDB container on AWS ECS, we recently changed the index-version from inmem to tsi1, and RESTARTED the ECS container. however when I inspect from [http://myinflux:8086/debug/vars](http://myinflux:8086/debug/vars), i can only see a lot node is called tsm1\_\* and the memory consumption does not change, looks like the configuration does not apply and influxDB still uses memory as 1st priority. Since we allocate 16GB for the container, my question is would InfluxDB only start to use disk for storing those index/cache files instead of memory, ONLY AFTER the memory limit is hit?