EDBT 2026 Demo / reviewers in the wild / expert
Kushal Wadhwani
dblp:124/5782
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2016
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Systems, architecture and hardware · 1
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Storage systems · 62% Cloud and datacenter computing · 38% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Storage systems
i/o workload characterization |
0.2 | 1 | 2016 | Storage Workload Identification · ACM Trans. Storage 2016 |
Cloud and datacenter computing
cloud storage |
0.1 | 1 | 2016 | Storage Workload Identification · ACM Trans. Storage 2016 |
Cloud and datacenter computing › cluster resource management and scheduling
workload colocation |
0.1 | 1 | 2016 | Storage Workload Identification · ACM Trans. Storage 2016 |
Methods — techniques the papers use, named apart from their topics
trace analysis · 0.2pattern matching · 0.2
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2016 | Storage Workload IdentificationabstractStorage workload identification is the task of characterizing a workload in a storage system (more specifically, network storage system—NAS or SAN) and matching it with the previously known workloads. We refer to storage workload identification as “workload identification” in the rest of this article. Workload identification is an important problem for cloud providers to solve because (1) providers can leverage this information to colocate similar workloads to make the system more predictable and (2) providers can identify workloads and subsequently give guidance to the subscribers as to associated best practices (with respect to configuration) for provisioning those workloads. Historically, people have identified workloads by looking at their read/write ratios, random/sequential ratios, block size, and interarrival frequency. Researchers are well aware that workload characteristics change over time and that one cannot just take a point in time view of a workload, as that will incorrectly characterize workload behavior. Increasingly, manual detection of workload signature is becoming harder because (1) it is difficult for a human to detect a pattern and (2) representing a workload signature by a tuple consisting of average values for each of the signature components leads to a large error. In this article, we present workload signature detection and a matching algorithm that is able to correctly identify workload signatures and match them with other similar workload signatures. We have tested our algorithm on nine different workloads generated using publicly available traces and on real customer workloads running in the field to show the robustness of our approach. Jayanta Basak, Kushal Wadhwani, Kaladhar Voruganti |
ACM Trans. Storage | 2 |