Proceedings of the 2007 Workshop on Experimental Computer Science 2007
DOI: 10.1145/1281700.1281702
|View full text |Cite
|
Sign up to set email alerts
|

Quantifying the cost of context switch

Abstract: Measuring the indirect cost of context switch is a challenging problem. In this paper, we show our results of experimentally quantifying the indirect cost of context switch using a synthetic workload. Specifically, we measure the impact of program data size and access stride on context switch cost. We also demonstrate the potential impact of OS background interrupt handling on the measurement accuracy. Such impact can be alleviated by using a multi-processor system on which one processor is employed for contex… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
63
0

Year Published

2010
2010
2023
2023

Publication Types

Select...
4
3
3

Relationship

0
10

Authors

Journals

citations
Cited by 143 publications
(65 citation statements)
references
References 4 publications
0
63
0
Order By: Relevance
“…A context switch can have a significant cost, although the cost may depend vastly on a variety of factors such as the processor type, workload, and memory access patterns of the applications between which the context switch is performed. As discussed in [20,5], the overhead of a context switch comes from several aspectsthe processor registers need to be saved and restored, cache and translation lookaside buffer (TLB) entries for the evicted process need to be flushed and then reloaded for the incoming process, and the processor pipeline must be flushed.…”
Section: Performance Overhead Of Fusementioning
confidence: 99%
“…A context switch can have a significant cost, although the cost may depend vastly on a variety of factors such as the processor type, workload, and memory access patterns of the applications between which the context switch is performed. As discussed in [20,5], the overhead of a context switch comes from several aspectsthe processor registers need to be saved and restored, cache and translation lookaside buffer (TLB) entries for the evicted process need to be flushed and then reloaded for the incoming process, and the processor pipeline must be flushed.…”
Section: Performance Overhead Of Fusementioning
confidence: 99%
“…The cost of a context switch can vary significantly [35,23]. On our platform, a simple benchmark where two threads take turns blocking each other on a synchronization variable estimates the context switch duration to be 3.3 µs.…”
Section: Thread Scheduling Overheadmentioning
confidence: 99%
“…As the algorithm is intended for real-time simulation, at 30 frames (steps) per second it must perform 30 × 160 = 4800 convolutions per second, or one every 200 microseconds. This interval is of the same order of magnitude as the context switch latency on a typical desktop operating system [7]. When benchmarking the fluid solver using ThreadScope [4], we noticed that for a grid of size 100 × 100 it was spending over half its time stalled while waiting for worker threads to be scheduled.…”
Section: Scheduling and Smallness Hintsmentioning
confidence: 99%