![]() ![]() ![]() There is no blocking in Async programming, so we don’t have to wait the slow I/O and can do other things. What’s more, frequent thread switching is inefficient and causes the performance to reduce seriously. Although we can use threads, but thread is heavy and wastes system resources. Sync I/O can block the execution, which reduces the performance. You just need to start some threads to handle the concurrence.īut if we want to support a high performance service, such as a database, Sync is not enough. If the load of your service is low, using Sync may be better. As we all know, the Sync programming is easier. Then I will talk about gRPC, and in the end, I will show you how we use futures to wrap the gRPC in Rust. Of course, you guys here are very familiar with them, so I will just go through it quickly. Today, I will first discuss Async briefly, then I will introduce Futures in Rust. I’m also an open source lover, and have some open source projects, such as LedisDB, go-mysql, go-mysql-elasticsearch, rust-prometheus, etc. By the way, TiKV is also written in Rust. I have been working on the next generation SQL database, TiDB, and a distributed key-value store, TiKV. My name is Siddon Tang, and siddontang on Github, chief engineer at PingCAP. Before we start, let me introduce myself briefly. Today I will talk about the Futures and gRPC in Rust. Hi everyone! I am very glad to join the meetup here. This is the speech Tang Liu gave at the Bay Area Rust Meetup August 2017. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |