Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Back to post

Revisions 2

Why does TON take seconds to process a transaction if it is capable of processing millions of transactions per second?
Why does TON take seconds to process a transaction if it is capable of processing millions of transactions per second?
It's said that TON blockchain is capable of processing millions of transactions per second. That sounds like it only needs to spend a small fraction of a second on each transaction. Why does every transactions take several seconds to complete, then? Why not a small fraction of a second? --- > This question was imported from Telegram Chat: https://t.me/tondev/127629
It's said that TON blockchain is capable of processing millions of transactions per second. That sounds like it only needs to spend a small fraction of a second on each transaction. Why does every transactions take several seconds to complete, then? Why not fraction of a second? --- > This question was imported from Telegram Chat: https://t.me/tondev/127629
#architecture
#architecture
7 months ago
Original
Why does TON take seconds to process a transaction if it is capable of processing millions of transactions per second?

It's said that TON blockchain is capable of processing millions of transactions per second. That sounds like it only needs to spend a small fraction of a second on each transaction. Why does every transactions take several seconds to complete, then? Why not fraction of a second? --- > This question was imported from Telegram Chat: https://t.me/tondev/127629
#architecture