Mingfang Ji

dblp:423/7643 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
1since 2021 · last 2026
0009-0007-0691-7994ORCID · reported

Domains — the database's venue-derived domains; a paper can count in several

Systems, architecture and hardware · 1 · 1 since 2021

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.

Artificial intelligence
1 paper
Efficient and distributed learning · 77% Language models and text generation · 23%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Cloud and datacenter computing · 100%

Topics — the 3 heaviest of 3, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Machine learning › Efficient and distributed learning
inference serving
1.012026
PARD: Enhancing Goodput for Inference Pipeline via Proactive Request Dropping · EuroSys 2026
Cloud and datacenter computing
cluster resource management and scheduling
1.012026
PARD: Enhancing Goodput for Inference Pipeline via Proactive Request Dropping · EuroSys 2026
Natural language and speech › Language models and text generation
large language model
0.312026
PARD: Enhancing Goodput for Inference Pipeline via Proactive Request Dropping · EuroSys 2026

Methods — techniques the papers use, named apart from their topics

proactive request dropping · 2.0latency-aware scheduling · 2.0
YearPublicationVenuePosition
2026 PARD: Enhancing Goodput for Inference Pipeline via Proactive Request Dropping
abstract
Modern deep neural network (DNN) and large language model (LLM) applications integrate multiple models into inference pipelines with stringent latency requirements for customized tasks. To mitigate extensive request timeouts caused by accumulation, systems for inference pipelines commonly drop a subset of requests so the remaining ones can satisfy latency constraints. Since it is commonly believed that request dropping adversely affects goodput, existing systems only drop requests when they have to, which we call reactive dropping. However, this reactive policy can not maintain high goodput, as it neither makes timely dropping decisions nor identifies the proper set of requests to drop, leading to issues of dropping requests too late or dropping the wrong set of requests.
Yitao Hu, Mingfang Ji, Wei Yang 0013, Yuhao Zhang 0006, Laiping Zhao, Wenxin Li 0001, Xiulong Liu 0001, Wenyu Qu, Hao Wang 0022
EuroSys4