liutao

Results 10 comments of liutao

Thank you for your prompt response. Besides tokio, does wasmtime have any other I/O solutions? Or is there any configuration on wasmtime that can improve tokio's io performance a bit?

Thank you very much for explaining the reasons for choosing tokio in such detail. Currently, I am using [FlashDB ](https://github.com/armink/FlashDB?tab=readme-ov-file) as my database. [FlashDB ](https://github.com/armink/FlashDB?tab=readme-ov-file) has two types of file...

Hi @pchickey,thank you for your modification tips. After I made the following changes according to your tips, the performance of wasmtime has been greatly improved. ![image](https://github.com/bytecodealliance/wasmtime/assets/10509166/1ceb425a-a1d7-4344-b970-ab1ed0e6bfa0) ![image](https://github.com/bytecodealliance/wasmtime/assets/10509166/3988e271-3584-4ec9-9e06-1f17824ec487) In the above...

> Thanks for testing that out @liutao-liu! I think it'd be reasonable to land something along these lines into the CLI itself, although I'd personally prefer to avoid a flag...

> Thanks for testing that out @liutao-liu! I think it'd be reasonable to land something along these lines into the CLI itself, although I'd personally prefer to avoid a flag...

> Sorry, but to confirm, did you keep the changes [mentioned above](https://github.com/bytecodealliance/wasmtime/issues/7973#issuecomment-1984961122), e.g. the `--block-file-io-in-tokio` flag? > > I sketched out what those changes might look like [in this commit](https://github.com/alexcrichton/wasmtime/commit/427ec065d11f80c7568ceed0dc280b11afc81af9),...

> Oops sorry I forgot to actually turn the option on. I do realize that the goal is to avoid `spawn_blocking`, and most of the patch I linked was doing...

//hi @pchickey, I'm still working on optimizing wasmtime's fd_read\fd_write performance, and I've found ```BorrowChecker``` to be a performance hotspot, at around 7% cpu. I looked at the history of commits...

Wasmtime's ```borrow checker``` should be modeled after Rust's ```borrow checker```, right? The ```borrow checker``` of Rust will only be executed by the compiler in the static code analysis phase, so...

[Issue#734]( https://github.com/bytecodealliance/wasmtime/issues/734) have some explaination of the backgroud of ```borrow checker```, the ```proposal``` mentioned in the issue is which proposal?