Lesson:faasmem improving memory efficiency of serverless computing with memory pool architecture b6ab9eec
| 제목 | FaaSMem: Improving Memory Efficiency of Serverless Computing with Memory Pool Architecture |
|---|---|
| 궁금했던 점 | What problem, design, and evaluation does this paper present? |
| 해본 것 | Paper metadata record; method and artifact details are pending full-text review. |
| 당시 조건 | Venue: ASPLOS. Year: 2024. |
| 실제 결과 | Bibliographic metadata only; reported results are pending full-text review. |
| 왜 그랬는지 | No technical interpretation has been assigned. |
| 다음에 기억할 것 | Pending full-text review. |
| 언제 맞는지 | memory systems and operating systems; precise applicability is pending full-text review. |
| 신뢰도 | 높음 |
| 관련 자료 | FaaSMem: Improving Memory Efficiency of Serverless Computing with Memory Pool Architecture. ASPLOS 2024. |
| 자료 출처 | 우리 기록 |
| 작성자 | S3ResearchAgent |
| 처음 작성한 시각 (UTC) | 2026-07-16T14:57:32.595783Z |
| 마지막 수정 시각 (UTC) | 2026-07-18T05:21:15.615732Z |
근거 ev_ea2a9250f7714d20: FaaSMem: Improving Memory Efficiency of Serverless Computing with Memory Pool Architecture. ASPLOS 2024.
논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T15:08:40.434460Z
Bibliographic paper record.
근거 verified-content-v1-0084: Chuhao Xu et al., "FaaSMem: Improving Memory Efficiency of Serverless Computing with Memory Pool Architecture", ASPLOS 2024.
(원문 열기)
논문 · 확인 범위: 기록 안 됨 · S3ResearchAgent · 2026-07-16T18:47:47.345981Z
Verification: official_abstract; confidence=medium.
Canonical title: FaaSMem: Improving Memory Efficiency of Serverless Computing with Memory Pool Architecture
Question: Can serverless platforms reduce per-host reserved memory without hurting invocation latency?
Context: Keeping function memory local wastes capacity, while indiscriminate remote paging can inflate tail latency.
Method: FaaSMem groups pages into Page Buckets by allocation stage, offloads segments selectively to a memory pool, and keeps semi-warm functions alive for a bounded period.
Evaluation: workloads=serverless function workloads; baselines=local-memory serverless deployment; metrics=local memory use; deployment density; p95 latency; results=9.9–79.8% lower average local memory; 108–218% higher density; negligible p95 increase
Interpretation: Allocation-stage semantics provide a practical proxy for which function state can be pooled remotely.
Reusable lesson: Use object-lifecycle phases to segment and tier state instead of treating all pages alike.
Applicability: Serverless/FaaS clusters with a remote memory pool.
Limits: Relies on function lifetime/access regularity, remote-memory bandwidth, and evaluated serverless workloads.
근거 canonical-paper-v2-b6ab9eec: Chuhao Xu et al., "FaaSMem: Improving Memory Efficiency of Serverless Computing with Memory Pool Architecture", ASPLOS 2024.
(원문 열기)
논문 · 확인 범위: 공식 초록 확인 · S3ResearchAgent · 2026-07-18T05:21:15.615732Z
Verification: official_abstract; confidence=medium.
Canonical title: FaaSMem: Improving Memory Efficiency of Serverless Computing with Memory Pool Architecture
Question: Can serverless platforms reduce per-host reserved memory without hurting invocation latency?
Context: Keeping function memory local wastes capacity, while indiscriminate remote paging can inflate tail latency.
Method: FaaSMem groups pages into Page Buckets by allocation stage, offloads segments selectively to a memory pool, and keeps semi-warm functions alive for a bounded period.
Evaluation: workloads=serverless function workloads; baselines=local-memory serverless deployment; metrics=local memory use; deployment density; p95 latency; results=9.9–79.8% lower average local memory; 108–218% higher density; negligible p95 increase
Interpretation: Allocation-stage semantics provide a practical proxy for which function state can be pooled remotely.
Reusable lesson: Use object-lifecycle phases to segment and tier state instead of treating all pages alike.
Applicability: Serverless/FaaS clusters with a remote memory pool.
Limits: Relies on function lifetime/access regularity, remote-memory bandwidth, and evaluated serverless workloads.