2019 IEEE 21st International Conference on High Performance Computing and Communications; IEEE 17th International Conference On 2019
DOI: 10.1109/hpcc/smartcity/dss.2019.00036
|View full text |Cite
|
Sign up to set email alerts
|

Performance Prediction for the Apache Kafka Messaging System

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
14
0

Year Published

2020
2020
2024
2024

Publication Types

Select...
4
3
2

Relationship

0
9

Authors

Journals

citations
Cited by 38 publications
(17 citation statements)
references
References 12 publications
0
14
0
Order By: Relevance
“…4, we noted different periods where the frequency of messages is higher than those of other periods. In particular, we note the 00 minutes, minutes 30-33 and minutes [43][44][45][46] appear to represent busier periods, which could contribute to correlation in our data. We investigated the impact of the removal of these scheduled messages from our data.…”
Section: Resultsmentioning
confidence: 99%
See 1 more Smart Citation
“…4, we noted different periods where the frequency of messages is higher than those of other periods. In particular, we note the 00 minutes, minutes 30-33 and minutes [43][44][45][46] appear to represent busier periods, which could contribute to correlation in our data. We investigated the impact of the removal of these scheduled messages from our data.…”
Section: Resultsmentioning
confidence: 99%
“…Wu, Shang & Wolter analyzed the performance of Kafka using specific tuning parameters [46]. Their analysis concluded that the performance varied significantly depending on message type and system infrastructure.…”
Section: Related Workmentioning
confidence: 99%
“…This component is highly critical since each incoming event passes through it. The decision for Apache Kafka was made due its high-throughput, low-latency, resiliency and scalability [28]. As shown in Figure 3, two internal components are listening to the message queue for incoming events: the scope streamer and the storage sink.…”
Section: Architecturementioning
confidence: 99%
“…Clearly, it is not recommended for production. On the other hand, Kafka uses a fault-tolerant distributed streaming platform called Apache Kafka [46]. It also enables distributed ordering service, so that we can have multiple Orderer nodes to avoid a single point of failure [45], [47].…”
Section: ) Hyperledger Fabric Networkmentioning
confidence: 99%