EventBus 和Otto的区别

最新推荐文章于 2020-04-05 12:03:47 发布

翻译最新推荐文章于 2020-04-05 12:03:47 发布 · 1.7k 阅读

文章标签：

#EventBus #Otto #区别

android 专栏收录该内容

21 篇文章

订阅专栏

本文对比了Otto与EventBus在功能和性能上的差异，包括事件处理方法、命名约定、注解使用、事件继承、事件缓存、事件生产者等，并通过Android应用性能基准测试进行了实证分析。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

Otto is another event bus library for Android; actually it’s a fork of Guava’s EventBus. greenrobot’s EventBus and Otto share some basic semantics (register, post, unregister, …), but there are differences which the following table summarizes:

	EventBus	Otto
Declare event handling methods	Name conventions	Annotations
Event inheritance	Yes	Yes
Subscriber inheritance	Yes	No
Cache most recent events	Yes, sticky events	No
Event producers (e.g. for coding cached events)	No	Yes
Event delivery in posting thread	Yes (Default)	Yes
Event delivery in main thread	Yes	No
Event delivery in background thread	Yes	No
Aynchronous event delivery	Yes	No

Besides features, performance is another differentiator. To compare performance, we created an Android application, which is also part of this repository (EventBusPerformance). You can also run the app on your phone to benchmark different scenarios.

Benchmark results indicate that EventBus is significantly faster in almost every scenario:

	EventBus	Otto
Posting 1000 events, Android 2.3 emulator	~70% faster
Posting 1000 events, S3 Android 4.0	~110% faster
Register 1000 subscribers, Android 2.3 emulator	~10% faster
Register 1000 subscribers, S3 Android 4.0	~70% faster
Register subscribers cold start, Android 2.3 emulator	~350% faster
Register subscribers cold start, S3 Android 4.0	About the same