Demo Data from EDBT 2026 / reviewers in the wild / expert
Hiranya Jayathilaka
dblp:141/2123
· DBLP profile ↗
8ranked-venue papers
7as first author
0since 2021 · last 2020
0000-0001-9558-8211ORCID · corroborated
Domains — the database's venue-derived domains; a paper can count in several
Systems, architecture and hardware · 3 · 3 first-authorDatabases, data management, data science and information retrieval · 2 · 2 first-authorApplied, interdisciplinary, general and emerging computing · 2 · 2 first-author
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 |
Cloud and datacenter computing · 87% Performance modeling and evaluation · 13% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Cloud and datacenter computing › cloud service management
cloud application management |
0.3 | 1 | 2017 | Performance Monitoring and Root Cause Analysis for Cloud-hosted Web Applications · WWW 2017 |
Cloud and datacenter computing › cloud service models
platform-as-a-service |
0.3 | 1 | 2017 | Performance Monitoring and Root Cause Analysis for Cloud-hosted Web Applications · WWW 2017 |
Performance modeling and evaluation
performance monitoring |
0.1 | 1 | 2017 | Performance Monitoring and Root Cause Analysis for Cloud-hosted Web Applications · WWW 2017 |
Methods — techniques the papers use, named apart from their topics
platform-level instrumentation · 0.3metadata injection · 0.3
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2020 | Detecting Performance Anomalies in Cloud Platform ApplicationsabstractWe present Roots, a full-stack monitoring and analysis system for performance anomaly detection and bottleneck identification in cloud platform-as-a-service (PaaS) systems. Roots facilitates application performance monitoring as a core capability of PaaS clouds, and relieves the developers from having to instrument application code. Roots tracks HTTP/S requests to hosted cloud applications and their use of PaaS services. To do so it employs lightweight monitoring of PaaS service interfaces. Roots processes this data in the background using multiple statistical techniques that in combination detect performance anomalies (i.e. violations of service-level objectives). For each anomaly, Roots determines whether the event was caused by a change in the request workload or by a performance bottleneck in a PaaS service. By correlating data collected across different layers of the PaaS, Roots is able to trace high-level performance anomalies to bottlenecks in specific components in the cloud platform. We implement Roots using the AppScale PaaS and evaluate its overhead and accuracy. Hiranya Jayathilaka, Chandra Krintz, Richard Wolski |
IEEE Trans. Cloud Comput. | 1 |
| 2017 | Performance Monitoring and Root Cause Analysis for Cloud-hosted Web ApplicationsabstractIn this paper, we describe Roots - a system for automatically identifying the "root cause" of performance anomalies in web applications deployed in Platform-as-a-Service (PaaS) clouds. Roots does not require application-level instrumentation. Instead, it tracks events within the PaaS cloud that are triggered by application requests using a combination of metadata injection and platform-level instrumentation. Hiranya Jayathilaka, Chandra Krintz, Richard Wolski |
WWW | 1 |
| 2015 | Response time service level agreements for cloud-hosted web applicationsabstractCloud computing is a successful model for hosting web-facing applications that are accessed by their users as services. While clouds currently offer Service Level Agreements (SLAs) containing guarantees of availability, they do not make performance guarantees for deployed applications. Hiranya Jayathilaka, Chandra Krintz, Richard Wolski |
SoCC | 1 |
| 2015 | Service-Level Agreement Durability for Web Service Response TimeabstractCloud computing is an attractive model for deploying web services in a highly scalable manner. Users access such cloud-hosted services via their web-facing application programming interfaces (APIs). Prior work has shown that it is possible to use a combined approach of static analysis and cloud platform monitoring to predict the response time upper bounds of such web APIs. This technique can be employed to automatically generate service level agreements (SLAs) concerning the performance of cloud-hosted web APIs. In this work, we explore the validity period of auto-generated SLAs in cloud settings. We discuss a simple model by which API consumers can establish a response time SLA with the cloud platform, and renegotiate it when/if the SLA becomes invalid due to the dynamic nature of the cloud. Using empirical methods and simulations on a real world public cloud platform, we show that it is possible to auto-generatehighly durable response time SLAs for cloud-hosted web APIs, thereby keeping the number of SLA invalidations and renegotiations very low, over long periods. Hiranya Jayathilaka, Chandra Krintz, Richard Wolski |
CloudCom | 1 |
| 2015 | EAGER: Deployment-Time API Governance for Modern PaaS CloudsabstractTo track, control, and compel reuse of web APIs, we investigate a new approach to API governance -- combined policy, implementation, and deployment control of web APIs. Our approach, called EAGER, provides a software architecture that integrates into PaaS platforms to support systemwide, deployment-time enforcement of governance policies. Specifically, EAGER checks for and prevents backward incompatible API changes from being deployed into production PaaS clouds, enforces service reuse, and facilitates enforcement of other best practices in software maintenance via policies. Our experiments with an EAGER prototype show that enforcing API governance at deployment-time in PaaS clouds is efficient and scalable to thousands of APIs and policies. Hiranya Jayathilaka, Chandra Krintz, Richard Wolski |
IC2E | 1 |
| 2014 | Cloud Platform Support for API GovernanceabstractAs scalable information technology evolves to a more cloud-like model, digital assets (code, data and software environments) increasingly require curation as web-accessible services. "Service-izing" digital assets consists of encapsulating assets in software that exposes them to web and mobile applications via well-defined yet flexible, network accessible, application programming interfaces (APIs). In this paper, we postulate that recent advances in cloud computing make cloud platforms as-a-service (PaaS) ideal for deployment, lifecycle management, and policy-based control i.e. API governance - for extant and future digital assets. Toward this end, we overview API governance as a PaaS technology and outline some early results generated by our investigation of a prototype we are developing, called EAGER, for implementing API governance at scale. Chandra Krintz, Hiranya Jayathilaka, Stratos Dimopoulos, Alexander Pucher, Richard Wolski, Tevfik Bultan |
IC2E | 2 |
| 2013 | Extending modern PaaS clouds with BSP to execute legacy MPI applicationsabstractAs the popularity of cloud computing continues to increase, a significant amount of legacy code implemented using older parallel computing standards is outdated and left behind. This forces the organizations to port the old applications into new cloud platforms. This, however, violates the "develop once - run anywhere" principle promised by utility computing. As a solution to this problem, we explore the possibility of executing unmodified MPI applications over a modern parallel computing platform. Using BSP as a bridging model between MPI and the Hadoop framework, we implement a prototype MPI runtime for today's computing clouds, which eliminates the overhead of porting legacy code. Hiranya Jayathilaka, Michael Agun |
SoCC | 1 |
| 2013 | Improved Server Architecture for Highly Efficient Message MediationabstractEnterprise Service Bus facilitates message-based communication between modular software components in a SOA application. In addition to message routing, the ESB communication abstraction includes filtering and transformation capabilities that enable composing separate software modules quickly, with minimal code changes. For this reason, this richer communication capability is often termed "mediation". Hiranya Jayathilaka, Pradeep R. Fernando, Paul Fremantle, Kasun Indrasiri, Dushan Abeyruwan, Supun Kamburugamuve, Sadeep Jayasumana, Sanjiva Weerawarana, Srinath Perera |
iiWAS | 1 |