We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
十几亿个的地址也可以在纳秒级判断完成(LevelDB的Key的数量过多会影响查询,所以用布隆过滤器)。这个放在v2.1里完善,之前是RPC暴露fsynctx的参数是临时方案,临时方案是应用层做新老地址判断,但是从Tx上链到Kafka再到ElasticSearch延时大,至少1分钟,比P2P广播慢了不少,需要应用层做重试补尝试机制,但是对于用户来说体验不好。这个要优化下。
The text was updated successfully, but these errors were encountered:
AlexiaChen
No branches or pull requests
十几亿个的地址也可以在纳秒级判断完成(LevelDB的Key的数量过多会影响查询,所以用布隆过滤器)。这个放在v2.1里完善,之前是RPC暴露fsynctx的参数是临时方案,临时方案是应用层做新老地址判断,但是从Tx上链到Kafka再到ElasticSearch延时大,至少1分钟,比P2P广播慢了不少,需要应用层做重试补尝试机制,但是对于用户来说体验不好。这个要优化下。
The text was updated successfully, but these errors were encountered: