diff --git a/documentation/tdenginedocs-en/advanced-features/index.html b/documentation/tdenginedocs-en/advanced-features/index.html index 0401fc37dc9ce5502409d162f240aeeb18bc3b71..cb8fd04c8ec0ef7c6941b49fb96526d9b8c5178c 100644 --- a/documentation/tdenginedocs-en/advanced-features/index.html +++ b/documentation/tdenginedocs-en/advanced-features/index.html @@ -29,7 +29,7 @@ INTERVAL(1M) SLIDING(30S)

Inside TDengine shell, you can use the command "show streams" to list the ongoing continuous queries, the command "kill stream" to kill a specific continuous query.

If you drop a table generated by the continuous query, the query will be removed too.

Publisher/Subscriber

-

Time series data is a sequence of data points over time. Inside a table, the data points are stored in order of timestamp. Also, there is a data retention policy, the data points will be removed once their lifetime is passed. From another view, a table in DTengine is just a standard message queue.

+

Time series data is a sequence of data points over time. Inside a table, the data points are stored in order of timestamp. Also, there is a data retention policy, the data points will be removed once their lifetime is passed. From another view, a table in TDengine is just a standard message queue.

To reduce the development complexity and improve data consistency, TDengine provides the pub/sub functionality. To publish a message, you simply insert a record into a table. Compared with popular messaging tool Kafka, you subscribe to a table or a SQL query statement, instead of a topic. Once new data points arrive, TDengine will notify the application. The process is just like Kafka.

The detailed API will be introduced in the connectors section.

Caching

@@ -38,4 +38,4 @@ INTERVAL(1M) SLIDING(30S)
select last(*) from thermometers where location=’beijing’

By this design, caching tool, like Redis, is not needed in the system. It will reduce the complexity of the system.

TDengine creates one or more virtual nodes(vnode) in each data node. Each vnode contains data for multiple tables and has its own buffer. The buffer of a vnode is fully separated from the buffer of another vnode, not shared. But the tables in a vnode share the same buffer.

-

System configuration parameter cacheBlockSize configures the cache block size in bytes, and another parameter cacheNumOfBlocks configures the number of cache blocks. The total memory for the buffer of a vnode is $cacheBlockSize \times cacheNumOfBlocks$. Another system parameter numOfBlocksPerMeter configures the maximum number of cache blocks a table can use. When you create a database, you can specify these parameters.

Back \ No newline at end of file +

System configuration parameter cacheBlockSize configures the cache block size in bytes, and another parameter cacheNumOfBlocks configures the number of cache blocks. The total memory for the buffer of a vnode is $cacheBlockSize \times cacheNumOfBlocks$. Another system parameter numOfBlocksPerMeter configures the maximum number of cache blocks a table can use. When you create a database, you can specify these parameters.

Back