Empirical observations con fi rm that systems are becoming increasingly con fi gurable 9 08 7/2010 7/2012 7/2014 Release time 1/1999 1/2003 1/2007 1/2011 0 1/2014 N Release time 02 1/2006 1/2010 1/2014 2.2.14 2.3.4 2.0.35 .3.24 Release time Apache 1/2006 1/2008 1/2010 1/2012 1/2014 0 40 80 120 160 200 2.0.0 1.0.0 0.19.0 0.1.0 Hadoop Number of parameters Release time MapReduce HDFS [Tianyin Xu, et al., “Too Many Knobs…”, FSE’15]
Empirical observations con fi rm that systems are becoming increasingly con fi gurable 10 nia San Diego, ‡Huazhong Univ. of Science & Technology, †NetApp, Inc tixu, longjin, xuf001, yyzhou}@cs.ucsd.edu kar.Pasupathy, Rukma.Talwadker}@netapp.com prevalent, but also severely software. One fundamental y of configuration, reflected parameters (“knobs”). With m software to ensure high re- aunting, error-prone task. nderstanding a fundamental users really need so many answer, we study the con- including thousands of cus- m (Storage-A), and hundreds ce system software projects. ng findings to motivate soft- ore cautious and disciplined these findings, we provide ich can significantly reduce A as an example, the guide- ters and simplify 19.7% of on existing users. Also, we tion methods in the context 7/2006 7/2008 7/2010 7/2012 7/2014 0 100 200 300 400 500 600 700 Storage-A Number of parameters Release time 1/1999 1/2003 1/2007 1/2011 0 100 200 300 400 500 5.6.2 5.5.0 5.0.16 5.1.3 4.1.0 4.0.12 3.23.0 1/2014 MySQL Number of parameters Release time 1/1998 1/2002 1/2006 1/2010 1/2014 0 100 200 300 400 500 600 1.3.14 2.2.14 2.3.4 2.0.35 1.3.24 Number of parameters Release time Apache 1/2006 1/2008 1/2010 1/2012 1/2014 0 40 80 120 160 200 2.0.0 1.0.0 0.19.0 0.1.0 Hadoop Number of parameters Release time MapReduce HDFS [Tianyin Xu, et al., “Too Many Knobs…”, FSE’15]
Performance distributions are multi-modal and have long tails • Certain con fi gurations can cause performance to take abnormally large values • Faulty con fi gurations take the tail values (worse than 99.99th percentile) • Certain con fi gurations can cause faults on multiple performance objectives. 13
Misconfiguration and its Effects ● Misconfigurations can elicit unexpected interactions between software and hardwar e
● These can result in non-functional fault s
○ Affecting non-functional system properties like latency, throughput, energy consumption, etc. 14 The system doesn’t crash or exhibit an obvious misbehavior Systems are still operational but with a degraded performance, e.g., high latency, low throughput, high energy consumption, high heat dissipation, or a combination of several
15 CUDA performance issue on tx2 When we are trying to transplant our CUDA source code from TX1 to TX2, it behaved strange. We noticed that TX2 has twice computing-ability as TX1 in GPU, as expectation, we think TX2 will 30% - 40% faster than TX1 at least. Unfortunately, most of our code base spent twice the time as TX1, in other words, TX2 only has 1/2 speed as TX1, mostly. We believe that TX2’s CUDA API runs much slower than TX1 in many cases. When we are trying to transplant our CUDA source code from TX1 to TX2, it behaved strange. We noticed that TX2 has twice computing-ability as TX1 in GPU, as expectation, we think TX2 will 30% - 40% faster than TX1 at least. Unfortunately, most of our code base spent twice the time as TX1, in other words, TX2 only has 1/2 speed as TX1, mostly. We believe that TX2’s CUDA API runs much slower than TX1 in many cases. The user is transferring the cod e
from one hardware to another When we are trying to transplant our CUDA source code from TX1 to TX2, it behaved strange. We noticed that TX2 has twice computing-ability as TX1 in GPU, as expectation, we think TX2 will 30% - 40% faster than TX1 at least. Unfortunately, most of our code base spent twice the time as TX1, in other words, TX2 only has 1/2 speed as TX1, mostly. We believe that TX2’s CUDA API runs much slower than TX1 in many cases. The target hardware is faster than the the source hardware .
User expects the code to run at least 30-40% faster. Motivating Example When we are trying to transplant our CUDA source code from TX1 to TX2, it behaved strange. We noticed that TX2 has twice computing-ability as TX1 in GPU, as expectation, we think TX2 will 30% - 40% faster than TX1 at least. Unfortunately, most of our code base spent twice the time as TX1, in other words, TX2 only has 1/2 speed as TX1, mostly. We believe that TX2’s CUDA API runs much slower than TX1 in many cases. The code ran 2x slower on the more powerful hardware
Motivating Example 16 June 3rd We have already tried this. We still have high latency. Any other suggestions? June 4th Please do the following and let us know if it works 1. Install JetPack 3.0 2. Set nvpmodel=MAX-N 3. Run jetson_clock.sh June 5th June 4th TX2 is pascal architecture. Please update your CMakeLists: + set(CUDA_STATIC_RUNTIME OFF )
.. .
+ -gencode=arch=compute_62,code=sm_62 The user had several misconfigurations In Software:
✖ Wrong compilation flags ✖ Wrong SDK version In Hardware:
✖ Wrong power mode ✖ Wrong clock/fan settings The discussions took 2 days Any suggestions on how to improve my performance? Thanks! How to resolve such issues faster? ?
0 500 1000 1500 Throughput (ops/sec) 0 1000 2000 3000 4000 5000 Average write latency ( s) The default con fi guration is typically bad and the optimal con fi guration is noticeably better than median 26 Default Con fi guration Optimal
Con fi guration better better • Default is ba d
• 2X-10X faster than worst • Noticeably faster than median
Causal AI in Systems and Software 30 Computer Architecture Database Operating Systems Programming Languages BigData Software Engineering https://github.com/y-ding/causal-system-papers
Why Causal Inference? (Simpson’s Paradox) 33 Increasing GPU memor y
increases Latency More GPU memory usage should reduce latency not increase it. Counterintuitive! Any ML-/statistical models built on this data will be incorrect !
Why Causal Inference? (Simpson’s Paradox) 34 Segregate data on swap memory Available swap memory is reducing GPU memory borrows memory from the swap for some intensive workloads. Other
host processes may reduce the available swap. Little will be left for the GPU to use.
35 Why Causal Inference? Real world problems can have 100s if not 1000s of interacting configuration options ! Manually understanding and evaluating each combination is impractical, if not impossible.
Load GPU Mem. Swap Mem. Latency Express the relationships between
interacting variables as a causal graph 36 Causal Performance Models Configuration option Direction(s) of the causality • Latency is affected by GPU Mem. which in turn is influenced by swap memory • External factors like resource pressure also affects swap memory Non-functional property System event
• Build a Causal Performance Model that capture the interactions options in the variability space using the observation performance data.
• Iterative causal performance model evaluation and model update • Perform downstream performance tasks such as performance debugging & optimization using Causal Reasoning UNICORN: Our Causal AI for Systems Method
UNICORN: Our Causal AI for Systems Method Software: DeepStream
Middleware: TF, TensorR T
Hardware: Nvidia Xavie r
Configuration: Default number of counters number of splitters latency (ms) 100 150 1 200 250 2 300 Cubic Interpolation Over Finer Grid 2 4 3 6 8 4 10 12 5 14 16 6 18 Budget Exhausted? Yes No 5- Update Causal Performance Model Query Engine 4- Estimate Causal Queries Estimate probability of satisfying QoS if BufferSize is set to 6k? 2- Learn Causal Performance Model Performanc e
Debugging Performanc e
Optimization 3- Translate Perf. Query
to Causal Queries •What is the root-cause of observed perf. fault ?
•How do I fix the misconfig. ?
•How can I improve throughput without sacrificing accuracy ?
•How do I understand perf behavior? Measure performance of the configuration(s) that maximizes information gain Performance Data Causal Model P(Th > 40/s|do(Buffersize = 6k)) 1- Specify
Configuration: Default number of counters number of splitters latency (ms) 100 150 1 200 250 2 300 Cubic Interpolation Over Finer Grid 2 4 3 6 8 4 10 12 5 14 16 6 18 Budget Exhausted? Yes No 5- Update Causal Performance Model Query Engine 4- Estimate Causal Queries Estimate probability of satisfying QoS if BufferSize is set to 6k? 2- Learn
Causal Perf. Model Performanc e
Debugging Performanc e
Optimization 3- Translate Performance Query
to Causal Queries •What is the root-cause of observed perf. fault ?
•How do I fix the misconfig. ?
•How can I improve throughput without sacrificing accuracy ?
•How do I understand perf behavior? Measure performance of the configuration(s) that maximizes information gain Performance Data Causal Model P(Th > 40/s|do(Buffersize = 6k)) 1- Specify
Performance Query QoS : Th > 40/s Observed : Th < 30/s ± 5/s UNICORN: Our Causal AI for Systems Method
Configuration: Default number of counters number of splitters latency (ms) 100 150 1 200 250 2 300 Cubic Interpolation Over Finer Grid 2 4 3 6 8 4 10 12 5 14 16 6 18 Budget Exhausted? Yes No 5- Update Causal Performance Model Query Engine 4- Estimate Causal Queries Estimate probability of satisfying QoS if BufferSize is set to 6k? 2- Learn
Causal Perf. Model Performanc e
Debugging Performanc e
Optimization 3- Translate Performance Query
to Causal Queries •What is the root-cause of observed perf. fault ?
•How do I fix the misconfig. ?
•How can I improve throughput without sacrificing accuracy ?
•How do I understand perf behavior? Measure performance of the configuration(s) that maximizes information gain Performance Data Causal Model P(Th > 40/s|do(Buffersize = 6k)) 1- Specify
Performance Query QoS : Th > 40/s Observed : Th < 30/s ± 5/s UNICORN: Our Causal AI for Systems Method
Hardware platforms in our experiments The reason behind using di ff erent types of hardware platforms is that they exhibit di ff erent behaviors due to di ff erences in terms of resources, their microarchitecture, etc. 45 AWS DeepLens:
Cloud-connected device System on Chip (SoC) Microcontrollers (MCUs)
Measuring performance for systems involves lots of challenges Each hardware requires di ff erent ways of instrumentations and clean measurement that contains least amount of noise is the most challenging part of our experiments. 46
Configuration: Default number of counters number of splitters latency (ms) 100 150 1 200 250 2 300 Cubic Interpolation Over Finer Grid 2 4 3 6 8 4 10 12 5 14 16 6 18 Budget Exhausted? Yes No 5- Update Causal Performance Model Query Engine 4- Estimate Causal Queries Estimate probability of satisfying QoS if BufferSize is set to 6k? 2- Learn
Causal Perf. Model Performanc e
Debugging Performanc e
Optimization 3- Translate Performance Query
to Causal Queries •What is the root-cause of observed perf. fault ?
•How do I fix the misconfig. ?
•How can I improve throughput without sacrificing accuracy ?
•How do I understand perf behavior? Measure performance of the configuration(s) that maximizes information gain Performance Data Causal Model P(Th > 40/s|do(Buffersize = 6k)) 1- Specify
Performance Query QoS : Th > 40/s Observed : Th < 30/s ± 5/s UNICORN: Our Causal AI for Systems Method
52 Diagnose and fix the root-cause of misconfigurations that cause non-functional faults Objective Causal Debugging: An example of downstream performance task Ὂ Use causal models to model various cross-stack configuration interactions; an d
Ὂ Counterfactual reasoning to recommend fixes for these misconfigurations Approach
Best Query Counterfactual Queries Rank Paths What if questions .
E.g., What if the configuration option X was set to a value ‘x’? Extract Causal Paths 54 Extracting Causal Paths from the Causal Model • What is the root-cause of my fault ?
• How do I fix my misconfigurations to improve performance? Misconfiguration Fault
fixed? Observational Data Build Causal Graph Yes No updat e
observationa l
data About 25 sample configurations (training data)
Extracting Causal Paths from the Causal Model Problem ✕ In real world cases, this causal graph can be very complex
✕ It may be intractable to reason over the entire graph directly 55 Solution ✓ Extract paths from the causal graph ✓ Rank them based on their Average Causal Effect on latency, etc. ✓ Reason over the top K paths
Extracting Causal Paths from the Causal Model 56 GPU Mem. Latency Swap Mem. Extract paths Always begins with a configuration option Or a system event Always terminates at a performance objective Load GPU Mem. Latency Swap Mem. Swap Mem. Latency Load GPU Mem.
Ranking Causal Paths from the Causal Model 57 ● They may be too many causal path s
● We need to select the most useful one s
● Compute the Average Causal Effect (ACE) of each pair of neighbors in a path GPU Mem. Swap Mem. Latency 𝐴𝐶 𝐸 (GPU Mem . , Swap) = 1 𝑁 ∑ 𝑎 , 𝑏 ∈ 𝑍 𝔼 (GPU Mem . 𝑑 𝑜 (Swap = 𝑏 )) − 𝔼 (GPU Mem . 𝑑 𝑜 (Swap = 𝑎 )) Expected value of GPU Mem. when we artificially intervene by setting Swap to the value b Expected value of GPU Mem. when we artificially intervene by setting Swap to the value a If this difference is large, then small changes to Swap Mem. will cause large changes to GPU Mem. Average over all permitted values of Swap memory.
Ranking Causal Paths from the Causal Model 58 ● Average the ACE of all pairs of adjacent nodes in the pat h
● Rank paths from highest path ACE (PACE) score to the lowes t
● Use the top K paths for subsequent analysis 𝑃𝐴𝐶𝐸 ( 𝑍 , 𝑌 ) = 1 2 ( 𝐴 𝐶 𝐸 ( 𝑍 , 𝑋 ) + 𝐴𝐶 𝐸 ( 𝑋 , 𝑌 )) X Y Z Sum over all pairs of nodes in the causal path. GPU Mem. Latency Swap Mem.
Best Query Counterfactual Queries Rank Paths What if questions .
E.g., What if the configuration option X was set to a value ‘x’? Extract Causal Paths 59 Diagnosing and Fixing the Faults • What is the root-cause of my fault ?
• How do I fix my misconfigurations to improve performance? Misconfiguration Fault
fixed? Observational Data Build Causal Graph Yes No updat e
observationa l
data About 25 sample configurations (training data)
Diagnosing and Fixing the Faults 60 ● Counterfactual inference asks “what if” questions about changes to the misconfigurations We are interested in the scenario where:
• We hypothetically have low latency;
Conditioned on the following events :
• We hypothetically set the new Swap memory to 4 G b
• Swap Memory was initially set to 2 Gb • We observed high latency when Swap was set to 2 G b
• Everything else remains the same Example Given that my current swap memory is 2 Gb, and I have high latency. What is
the probability of having low latency if swap memory was increased to 4 Gb?
Diagnosing and Fixing the Faults 63 Potential = 𝑃 ( ^ 𝑜𝑢𝑡𝑐𝑜𝑚 𝑒 = 𝑔𝑜 𝑜𝑑 ~ ~ 𝑐 h 𝑎 𝑛 𝑔 𝑒 , ~ 𝑜 𝑢 𝑡𝑐𝑜 𝑚 𝑒 ¬ 𝑐 h 𝑎 𝑛 𝑔 𝑒 = 𝑏𝑎𝑑 , ~¬ 𝑐 h 𝑎 𝑛 𝑔𝑒 , 𝑈 ) Probability that the outcome is good after a change, conditioned on the past If this difference is large, then our change is useful Individual Treatment Effect = Potential − Outcome Control = 𝑃 ( ^ 𝑜𝑢 𝑡 𝑐 𝑜 𝑚 𝑒 = 𝑏𝑎𝑑 ~ ~¬ 𝑐 h 𝑎 𝑛𝑔 𝑒 , 𝑈 ) Probability that the outcome was bad before the change
Diagnosing and Fixing the Faults 64 GPU Mem. Latency Swap Mem. Top K paths ⋮ Enumerate all possible changes 𝐼 𝑇 𝐸 ( 𝑐 h 𝑎𝑛𝑔 𝑒 ) Change with the largest ITE Set every configuration option in the path to all permitted values Inferred from observed data. This is very cheap. !
Configuration: Default number of counters number of splitters latency (ms) 100 150 1 200 250 2 300 Cubic Interpolation Over Finer Grid 2 4 3 6 8 4 10 12 5 14 16 6 18 Budget Exhausted? Yes No 5- Update Causal Performance Model Query Engine 4- Estimate Causal Queries Estimate probability of satisfying QoS if BufferSize is set to 6k? 2- Learn
Causal Perf. Model Performanc e
Debugging Performanc e
Optimization 3- Translate Performance Query
to Causal Queries •What is the root-cause of observed perf. fault ?
•How do I fix the misconfig. ?
•How can I improve throughput without sacrificing accuracy ?
•How do I understand perf behavior? Measure performance of the configuration(s) that maximizes information gain Performance Data Causal Model P(Th > 40/s|do(Buffersize = 6k)) 1- Specify
Performance Query QoS : Th > 40/s Observed : Th < 30/s ± 5/s UNICORN: Our Causal AI for Systems Method
Padding 1- Evaluate Candidate Interventions FPS Energy Branch
Misses Cache
Misses No of
Cycles Bitrate Buffer
Size Batch
Size Enabl e
Padding Option/Event/Obj Values Bitrate 1k Buffer Size 20k Batch Size 10 Enable Padding 1 Branch Misses 24m Cache Misses 42m No of Cycles 73b FPS 31/s Energy 42J 2- Determine & Perform next Perf Measurement 3- Updating
Causal Model Performance
Data Model averaging Expected change in belief & KL; Causal effects on objectives Interventions on Hardware, Workload, and Kernel Options Active Learning for Updating Causal Performance Model
Padding 1- Evaluate Candidate Interventions FPS Energy Branch
Misses Cache
Misses No of
Cycles Bitrate Buffer
Size Batch
Size Enabl e
Padding Option/Event/Obj Values Bitrate 1k Buffer Size 20k Batch Size 10 Enable Padding 1 Branch Misses 24m Cache Misses 42m No of Cycles 73b FPS 31/s Energy 42J 2- Determine & Perform next Perf Measurement 3- Updating
Causal Model Performance
Data Model averaging Expected change in belief & KL; Causal effects on objectives Interventions on Hardware, Workload, and Kernel Options Active Learning for Updating Causal Performance Model
Padding 1- Evaluate Candidate Interventions FPS Energy Branch
Misses Cache
Misses No of
Cycles Bitrate Buffer
Size Batch
Size Enabl e
Padding Option/Event/Obj Values Bitrate 1k Buffer Size 20k Batch Size 10 Enable Padding 1 Branch Misses 24m Cache Misses 42m No of Cycles 73b FPS 31/s Energy 42J 2- Determine & Perform next Perf Measurement 3- Updating
Causal Model Performance
Data Model averaging Expected change in belief & KL; Causal effects on objectives Interventions on Hardware, Workload, and Kernel Options Active Learning for Updating Causal Performance Model
There are two fundamental benefits that we get by our “Causal AI for Systems” methodology 1. We learn one central (causal) performance model from the data across di ff erent performance tasks:
• Performance understanding
• Performance optimization
• Performance debugging and repair
• Performance prediction for di ff erent environments (e.g., canary-> production)
2. The causal model is transferable across environments.
• We observed Sparse Mechanism Shift in systems too!
• Alternative non-causal models (e.g., regression-based models for performance tasks) are not transferable as they rely on i.i.d. setting. 71
Questions of this nature require precise mathematical language lest they will be misleading. Here we are simultaneously conditioning on two values of GPU memory growth (i.e., 𝑋 ˆ = 0.66 and 𝑋 = 0.33). Traditional machine learning approaches cannot handle such expressions. Instead, we must resort to causal models to compute them. 72
Difference between statistical (left) and causal models (right) on a given set of three variables While a statistical model speci fi es a single probability distribution, a causal model represents a set of distributions, one for each possible intervention. 73
Sparse Mechanism Shift (SMS) Hypothesis Example of SMS hypothesis, where an intervention (which may or may not be intentional/observed) changes the position of one fi nger, and as a consequence, the object falls. The change in pixel space is entangled (or distributed), in contrast to the change in the causal model.
Results: Case Study 78 When we are trying to transplant our CUDA source code from TX1 to TX2, it behaved strange. We noticed that TX2 has twice computing-ability as TX1 in GPU, as expectation, we think TX2 will 30% - 40% faster than TX1 at least. Unfortunately, most of our code base spent twice the time as TX1, in other words, TX2 only has 1/2 speed as TX1, mostly. We believe that TX2’s CUDA API runs much slower than TX1 in many cases. When we are trying to transplant our CUDA source code from TX1 to TX2, it behaved strange. We noticed that TX2 has twice computing-ability as TX1 in GPU, as expectation, we think TX2 will 30% - 40% faster than TX1 at least. Unfortunately, most of our code base spent twice the time as TX1, in other words, TX2 only has 1/2 speed as TX1, mostly. We believe that TX2’s CUDA API runs much slower than TX1 in many cases. When we are trying to transplant our CUDA source code from TX1 to TX2, it behaved strange. We noticed that TX2 has twice computing-ability as TX1 in GPU, as expectation, we think TX2 will 30% - 40% faster than TX1 at least. Unfortunately, most of our code base spent twice the time as TX1, in other words, TX2 only has 1/2 speed as TX1, mostly. We believe that TX2’s CUDA API runs much slower than TX1 in many cases. When we are trying to transplant our CUDA source code from TX1 to TX2, it behaved strange. We noticed that TX2 has twice computing-ability as TX1 in GPU, as expectation, we think TX2 will 30% - 40% faster than TX1 at least. Unfortunately, most of our code base spent twice the time as TX1, in other words, TX2 only has 1/2 speed as TX1, mostly. We believe that TX2’s CUDA API runs much slower than TX1 in many cases. The user is transferring the cod e
from one hardware to another The target hardware is faster than the the source hardware .
User expects the code to run at least 30-40% faster. The code ran 2x slower on the more powerful hardware
Results: Case Study 80 Configuration CADET Decision Tree Forum CPU Cores ✓ ✓ ✓ CPU Freq. ✓ ✓ ✓ EMC Freq. ✓ ✓ ✓ GPU Freq. ✓ ✓ ✓ Sched. Policy ✓ Sched. Runtime ✓ Sched. Child Proc ✓ Dirty Bg. Ratio ✓ Drop Caches ✓ CUDA_STATIC_R T ✓ ✓ ✓ Swap Memory ✓ CADET Decision Tree Forum Throughput (on TX2) 26 FPS 20 FPS 23 FPS Throughput Gain (over TX1) 53 % 21 % 39 % Time to resolve 24 min. 31/2 Hrs. 2 days X Finds the root-causes accuratel y
X No unnecessary change s
X Better improvements than forum’s recommendatio n
X Much faster Results The user expected 30-40% gain
Evaluation: Data Collection ● For each software/hardware combination create a benchmark datase t
○ Exhaustively set each of configuration option to all permitted values. ○ For continuous options (e.g., GPU memory Mem.), sample 10 equally spaced values between [min, max] ● Measure the latency, energy consumption, and heat dissipatio n
○ Repeat 5x and average 82 Multiple Faults ! Latency Faults ! Energy Faults !
Evaluation: Ground Truth ● For each performance fault :
○ Manually investigate the root-cause ○ “Fix” the misconfigurations ● A “fix” implies the configuration no longer has tail performanc e
○ User defined benchmark (i.e., 10th percentile) ○ Or some QoS/SLA benchmark ● Record the configurations that were changed 83 Multiple Faults ! Latency Faults ! Energy Faults !
85 RQ1: How does CADET perform compared to Model based Diagnostics RQ2: How does CADET perform compared to Search-Based Optimization Results: Research Questions
86 Results: Research Question 1 (single objective) RQ1: How does CADET perform compared to Model based Diagnostics X Finds the root-causes accurately X Better gain X Much faster Takeaways More accurate tha n
87 Results: Research Question 1 (multi-objective) RQ1: How does CADET perform compared to Model based Diagnostics X No deterioration of other performance objectives Takeaways Multiple Fault s
88 RQ1: How does CADET perform compared to Model based Diagnostics RQ2: How does CADET perform compared to Search-Based Optimization Results: Research Questions
Results: Research Question 2 RQ2: How does CADET perform compared to Search-Based Optimization X Better with no deterioration of other performance objectives Takeaways 89
90 Results: Research Question 3 RQ2: How does CADET perform compared to Search-Based Optimization X Considerably faster than search-based optimization Takeaways
Causal AI for Autonomous Robot Testing • Testing cyberphysical systems such as robots are di ff i cult. The key reason is that there are additional interactions with the environment and the task that the robot is performing.
• Evaluating our Causal AI for Systems methodology with autonomous robots provide the following opportunities:
1. Identifying di ff i cult to catch bugs in robots
2. Identifying the root cause of an observed fault and repairing the issue automatically during mission time. 93
Summary: Causal AI for Systems 1. Learning a Functional Causal Model for di ff erent downstream systems tasks
2. The learned causal model is transferable across di ff erent environments 94 Software: DeepStream
Middleware: TF, TensorR T
Hardware: Nvidia Xavie r
Configuration: Default number of counters number of splitters latency (ms) 100 150 1 200 250 2 300 Cubic Interpolation Over Finer Grid 2 4 3 6 8 4 10 12 5 14 16 6 18 Budget Exhausted? Yes No 5- Update Causal Performance Model Query Engine 4- Estimate Causal Queries Estimate probability of satisfying QoS if BufferSize is set to 6k? 2- Learn Causal Performance Model Performanc e
Debugging Performanc e
Optimization 3- Translate Perf. Query
to Causal Queries •What is the root-cause of observed perf. fault ?
•How do I fix the misconfig. ?
•How can I improve throughput without sacrificing accuracy ?
•How do I understand perf behavior? Measure performance of the configuration(s) that maximizes information gain Performance Data Causal Model P(Th > 40/s|do(Buffersize = 6k)) 1- Specify
pjamshidi
.png){kind=avatar}
researchconf
satotaichi
shuntaros
isayan
yuyay
yosukefk
masakat0
smartfukushilab1
shotasasaki
ryou0634
kuri8ive
sferik
maltzj
mojombo
moore
hursman
frogandcode
paigeccino
brad_frost
reverentgeek
yeseniaperezcruz
rocio
nonsquared