WPC: Whole-picture Workload Characterization

This article raises an important and challenging workload characterization issue: can we uncover each critical component across the stacks contributing what percentages to any specific bottleneck? The typical critical components include languages, programming frameworks, runtime environments, instru...

Ausführliche Beschreibung

Gespeichert in:
Bibliographische Detailangaben
Hauptverfasser: Wang, Lei, Yang, Kaiyong, Wang, Chenxi, Gao, Wanling, Luo, Chunjie, Zhang, Fan, Ge, Zhongxin, Zhang, Li, Kang, Guoxin, Zhan, Jianfeng
Format: Artikel
Sprache:eng
Schlagworte:
Online-Zugang:Volltext bestellen
Tags: Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
container_end_page
container_issue
container_start_page
container_title
container_volume
creator Wang, Lei
Yang, Kaiyong
Wang, Chenxi
Gao, Wanling
Luo, Chunjie
Zhang, Fan
Ge, Zhongxin
Zhang, Li
Kang, Guoxin
Zhan, Jianfeng
description This article raises an important and challenging workload characterization issue: can we uncover each critical component across the stacks contributing what percentages to any specific bottleneck? The typical critical components include languages, programming frameworks, runtime environments, instruction set architectures (ISA), operating systems (OS), and microarchitecture. Tackling this issue could help propose a systematic methodology to guide the software and hardware co-design and critical component optimizations. We propose a whole-picture workload characterization (WPC) methodology to answer the above issue. In essence, WPC is an iterative ORFE loop consisting of four steps: Observation, Reference, Fusion, and Exploration. WPC observes different level data (observation), fuses and normalizes the performance data (fusion) with respect to the well-designed standard reference workloads suite (reference), and explores the software and hardware co-design space (exploration) to investigate the impacts of critical components across the stacks. We build and open-source the WPC tool. Our evaluations confirm WPC can quantitatively reveal the contributions of the language, framework, runtime environment, ISA, OS, and microarchitecture to the primary pipeline efficiency.
doi_str_mv 10.48550/arxiv.2302.12954
format Article
fullrecord <record><control><sourceid>arxiv_GOX</sourceid><recordid>TN_cdi_arxiv_primary_2302_12954</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><sourcerecordid>2302_12954</sourcerecordid><originalsourceid>FETCH-LOGICAL-a674-37e10ff892fb8fa12db8c39b2de8d30f98956f248c145c2dc59876c16bae7d0e3</originalsourceid><addsrcrecordid>eNotzjkKwkAYQOFpLEQ9gJU5gImzJjN2EtxA0EJIGf7MgoPRyBhFPb24VK97fAgNCU64FAJPIDz8PaEM04RQJXgXjYtdPo2KQ1Pb-OJ1ews2KppwrBswUX6AALq1wb-g9c25jzoO6qsd_NtD-8V8n6_izXa5zmebGNKMxyyzBDsnFXWVdECoqaRmqqLGSsOwU1KJ1FEuNeFCU6OFklmqSVqBzQy2rIdGv-2XW16CP0F4lh92-WWzN_coPKI</addsrcrecordid><sourcetype>Open Access Repository</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype></control><display><type>article</type><title>WPC: Whole-picture Workload Characterization</title><source>arXiv.org</source><creator>Wang, Lei ; Yang, Kaiyong ; Wang, Chenxi ; Gao, Wanling ; Luo, Chunjie ; Zhang, Fan ; Ge, Zhongxin ; Zhang, Li ; Kang, Guoxin ; Zhan, Jianfeng</creator><creatorcontrib>Wang, Lei ; Yang, Kaiyong ; Wang, Chenxi ; Gao, Wanling ; Luo, Chunjie ; Zhang, Fan ; Ge, Zhongxin ; Zhang, Li ; Kang, Guoxin ; Zhan, Jianfeng</creatorcontrib><description>This article raises an important and challenging workload characterization issue: can we uncover each critical component across the stacks contributing what percentages to any specific bottleneck? The typical critical components include languages, programming frameworks, runtime environments, instruction set architectures (ISA), operating systems (OS), and microarchitecture. Tackling this issue could help propose a systematic methodology to guide the software and hardware co-design and critical component optimizations. We propose a whole-picture workload characterization (WPC) methodology to answer the above issue. In essence, WPC is an iterative ORFE loop consisting of four steps: Observation, Reference, Fusion, and Exploration. WPC observes different level data (observation), fuses and normalizes the performance data (fusion) with respect to the well-designed standard reference workloads suite (reference), and explores the software and hardware co-design space (exploration) to investigate the impacts of critical components across the stacks. We build and open-source the WPC tool. Our evaluations confirm WPC can quantitatively reveal the contributions of the language, framework, runtime environment, ISA, OS, and microarchitecture to the primary pipeline efficiency.</description><identifier>DOI: 10.48550/arxiv.2302.12954</identifier><language>eng</language><subject>Computer Science - Performance</subject><creationdate>2023-02</creationdate><rights>http://creativecommons.org/licenses/by-nc-nd/4.0</rights><oa>free_for_read</oa><woscitedreferencessubscribed>false</woscitedreferencessubscribed></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><link.rule.ids>228,230,776,881</link.rule.ids><linktorsrc>$$Uhttps://arxiv.org/abs/2302.12954$$EView_record_in_Cornell_University$$FView_record_in_$$GCornell_University$$Hfree_for_read</linktorsrc><backlink>$$Uhttps://doi.org/10.48550/arXiv.2302.12954$$DView paper in arXiv$$Hfree_for_read</backlink></links><search><creatorcontrib>Wang, Lei</creatorcontrib><creatorcontrib>Yang, Kaiyong</creatorcontrib><creatorcontrib>Wang, Chenxi</creatorcontrib><creatorcontrib>Gao, Wanling</creatorcontrib><creatorcontrib>Luo, Chunjie</creatorcontrib><creatorcontrib>Zhang, Fan</creatorcontrib><creatorcontrib>Ge, Zhongxin</creatorcontrib><creatorcontrib>Zhang, Li</creatorcontrib><creatorcontrib>Kang, Guoxin</creatorcontrib><creatorcontrib>Zhan, Jianfeng</creatorcontrib><title>WPC: Whole-picture Workload Characterization</title><description>This article raises an important and challenging workload characterization issue: can we uncover each critical component across the stacks contributing what percentages to any specific bottleneck? The typical critical components include languages, programming frameworks, runtime environments, instruction set architectures (ISA), operating systems (OS), and microarchitecture. Tackling this issue could help propose a systematic methodology to guide the software and hardware co-design and critical component optimizations. We propose a whole-picture workload characterization (WPC) methodology to answer the above issue. In essence, WPC is an iterative ORFE loop consisting of four steps: Observation, Reference, Fusion, and Exploration. WPC observes different level data (observation), fuses and normalizes the performance data (fusion) with respect to the well-designed standard reference workloads suite (reference), and explores the software and hardware co-design space (exploration) to investigate the impacts of critical components across the stacks. We build and open-source the WPC tool. Our evaluations confirm WPC can quantitatively reveal the contributions of the language, framework, runtime environment, ISA, OS, and microarchitecture to the primary pipeline efficiency.</description><subject>Computer Science - Performance</subject><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>2023</creationdate><recordtype>article</recordtype><sourceid>GOX</sourceid><recordid>eNotzjkKwkAYQOFpLEQ9gJU5gImzJjN2EtxA0EJIGf7MgoPRyBhFPb24VK97fAgNCU64FAJPIDz8PaEM04RQJXgXjYtdPo2KQ1Pb-OJ1ews2KppwrBswUX6AALq1wb-g9c25jzoO6qsd_NtD-8V8n6_izXa5zmebGNKMxyyzBDsnFXWVdECoqaRmqqLGSsOwU1KJ1FEuNeFCU6OFklmqSVqBzQy2rIdGv-2XW16CP0F4lh92-WWzN_coPKI</recordid><startdate>20230224</startdate><enddate>20230224</enddate><creator>Wang, Lei</creator><creator>Yang, Kaiyong</creator><creator>Wang, Chenxi</creator><creator>Gao, Wanling</creator><creator>Luo, Chunjie</creator><creator>Zhang, Fan</creator><creator>Ge, Zhongxin</creator><creator>Zhang, Li</creator><creator>Kang, Guoxin</creator><creator>Zhan, Jianfeng</creator><scope>AKY</scope><scope>GOX</scope></search><sort><creationdate>20230224</creationdate><title>WPC: Whole-picture Workload Characterization</title><author>Wang, Lei ; Yang, Kaiyong ; Wang, Chenxi ; Gao, Wanling ; Luo, Chunjie ; Zhang, Fan ; Ge, Zhongxin ; Zhang, Li ; Kang, Guoxin ; Zhan, Jianfeng</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-a674-37e10ff892fb8fa12db8c39b2de8d30f98956f248c145c2dc59876c16bae7d0e3</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>2023</creationdate><topic>Computer Science - Performance</topic><toplevel>online_resources</toplevel><creatorcontrib>Wang, Lei</creatorcontrib><creatorcontrib>Yang, Kaiyong</creatorcontrib><creatorcontrib>Wang, Chenxi</creatorcontrib><creatorcontrib>Gao, Wanling</creatorcontrib><creatorcontrib>Luo, Chunjie</creatorcontrib><creatorcontrib>Zhang, Fan</creatorcontrib><creatorcontrib>Ge, Zhongxin</creatorcontrib><creatorcontrib>Zhang, Li</creatorcontrib><creatorcontrib>Kang, Guoxin</creatorcontrib><creatorcontrib>Zhan, Jianfeng</creatorcontrib><collection>arXiv Computer Science</collection><collection>arXiv.org</collection></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext_linktorsrc</fulltext></delivery><addata><au>Wang, Lei</au><au>Yang, Kaiyong</au><au>Wang, Chenxi</au><au>Gao, Wanling</au><au>Luo, Chunjie</au><au>Zhang, Fan</au><au>Ge, Zhongxin</au><au>Zhang, Li</au><au>Kang, Guoxin</au><au>Zhan, Jianfeng</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>WPC: Whole-picture Workload Characterization</atitle><date>2023-02-24</date><risdate>2023</risdate><abstract>This article raises an important and challenging workload characterization issue: can we uncover each critical component across the stacks contributing what percentages to any specific bottleneck? The typical critical components include languages, programming frameworks, runtime environments, instruction set architectures (ISA), operating systems (OS), and microarchitecture. Tackling this issue could help propose a systematic methodology to guide the software and hardware co-design and critical component optimizations. We propose a whole-picture workload characterization (WPC) methodology to answer the above issue. In essence, WPC is an iterative ORFE loop consisting of four steps: Observation, Reference, Fusion, and Exploration. WPC observes different level data (observation), fuses and normalizes the performance data (fusion) with respect to the well-designed standard reference workloads suite (reference), and explores the software and hardware co-design space (exploration) to investigate the impacts of critical components across the stacks. We build and open-source the WPC tool. Our evaluations confirm WPC can quantitatively reveal the contributions of the language, framework, runtime environment, ISA, OS, and microarchitecture to the primary pipeline efficiency.</abstract><doi>10.48550/arxiv.2302.12954</doi><oa>free_for_read</oa></addata></record>
fulltext fulltext_linktorsrc
identifier DOI: 10.48550/arxiv.2302.12954
ispartof
issn
language eng
recordid cdi_arxiv_primary_2302_12954
source arXiv.org
subjects Computer Science - Performance
title WPC: Whole-picture Workload Characterization
url https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-01-30T17%3A08%3A38IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-arxiv_GOX&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=WPC:%20Whole-picture%20Workload%20Characterization&rft.au=Wang,%20Lei&rft.date=2023-02-24&rft_id=info:doi/10.48550/arxiv.2302.12954&rft_dat=%3Carxiv_GOX%3E2302_12954%3C/arxiv_GOX%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_id=info:pmid/&rfr_iscdi=true