Skip to main content

Case Study: Semaphores

  • Chapter
  • First Online:
MySQL Concurrency
  • 792 Accesses

Abstract

Mutex and semaphore contention is one of the most elusive kinds of contention you can come across as except for extreme situations, you will not directly notice any issues. Instead, the contention tends to materialize as an overall added latency and throughput reduction that can be hard to put your finger on. Then out of the blue, you may have crossed a load threshold, and the contention causes your server to come to a grinding halt.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

eBook
USD 16.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 69.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2021 Jesper Wisborg Krogh

About this chapter

Check for updates. Verify currency and authenticity via CrossMark

Cite this chapter

Krogh, J.W. (2021). Case Study: Semaphores. In: MySQL Concurrency. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-6652-6_18

Download citation

Publish with us

Policies and ethics