Companion of the 2019 ACM/SPEC International Conference on Performance Engineering 2019
DOI: 10.1145/3302541.3311961
|View full text |Cite
|
Sign up to set email alerts
|

Pptam

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
5
0

Year Published

2019
2019
2023
2023

Publication Types

Select...
4
2
1

Relationship

2
5

Authors

Journals

citations
Cited by 12 publications
(5 citation statements)
references
References 6 publications
0
5
0
Order By: Relevance
“…In particular, we observed that more elaborate workloads (e.g., involving different APIs) may severely reduce the proportion of "ADC requests" in requests that violate SLO (i.e., with latency L > L SLO ). For example, when using PPTAM [54], which is an elaborated Train Ticket workload used in prior work [55], [56], we observed that only ∼19% of requests that violate SLO are assigned to an ADC. Such behavior have significant implications on the validity of our study, as our evaluation is based on the assumption that ADCs represent relevant causes of latency degradation.…”
Section: Methodsmentioning
confidence: 93%
See 1 more Smart Citation
“…In particular, we observed that more elaborate workloads (e.g., involving different APIs) may severely reduce the proportion of "ADC requests" in requests that violate SLO (i.e., with latency L > L SLO ). For example, when using PPTAM [54], which is an elaborated Train Ticket workload used in prior work [55], [56], we observed that only ∼19% of requests that violate SLO are assigned to an ADC. Such behavior have significant implications on the validity of our study, as our evaluation is based on the assumption that ADCs represent relevant causes of latency degradation.…”
Section: Methodsmentioning
confidence: 93%
“…For the Train Ticket case study, we use PPTAM [54] as a load generator, which involves 5 different user types (we refer to our replication package [52] for details on each user type). We slightly modified PPTAM to continuously change the number of users of each type at run-time.…”
Section: Methodsmentioning
confidence: 99%
“…For our pilot study, we are utilizing a dataset of traces that was generated in a previous work of the second author [40]. The dataset was created using the widely-used microservices benchmark system TrainTicket [16,26,[44][45][46], and the load generator PPTAM [4]. Our technology stack includes the use of Jaeger [38] as the distributed tracing collector and Elasticsearch [11] for storing both common and optimized traces.…”
Section: Ongoing Workmentioning
confidence: 99%
“…This approach generates a mixture of different request types that change dynamically, closely resembling real-world scenarios. We utilize Production and Performance Testing-based Application Monitoring (PPTAM) [21] as our load generator, which incorporates 5 distinct user types. We made slight modifications to PPTAM to ensure that the number of users for each request type changes continuously during runtime.…”
Section: ) Experimental Testbedmentioning
confidence: 99%