Abstract
Pub/sub messaging is a promising design pattern that relies on a centralized component called the broker, which routes messages to different devices. Due to its prominent role, the broker must be capable of providing high quality services under heavy workload. In this letter, we evaluate the resource consumption of state-of-the-art fuzzing frameworks, thereby understanding the degree to which brokers are tested before deployment. Our results attest that only one framework shows the most promise for memory-intensive testing, outperforming its counterparts by more than 20%. We conclude the letter by highlighting shortcomings that prevent existing frameworks from consuming considerable system resources.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
