actor-framework-bench

Benchmark Rust actor frameworks with same application

Target Frameworks

Actix

You can run the Actix example with:

cargo run --bin actix

Concepts

actix has 3 types for controlling concurrency

• OS process
  • out of scope of actix
• System
  • Usually, only one in process
  • Only for special reason, like test, there are multiple Systems.
  • Between different Systems, Actors cannot send messages.
• Arbiter
  • Represents a OS thread
  • Each Arbiter is bound to one and only one System
  • System can hold multiple Arbiters. But in this benchmark, we only use one Arbiter.
• Actor
  • Encapsulates state and behavior
  • Communicates with other Actors by sending and receiving messages
  • Each Actor is bound to one and only one Arbiter

Ractor

• cast: 片方向メッセージ送信
• call: RPC

Differences

• Timer

  • Actix: actix::AsyncContext::run_interval
  • Ractor: Not supported. Need to use tokio::time::interval and send message to Actor periodically.

• Handler

  • Actix: Need to implement Handler trait for each message type.
  • Ractor: Implement Actor trait once, and define message handling in handle method.