Add Buffer Management to SnappyInput Stream

未關閉
#274 1 則留言 1 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
42/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
停滯
技術堆疊
java
領域
backend

研究方向

Start by comparing buffer management in SnappyOutputStream with the allocation paths in SnappyInputStream, for both chunked and raw input. The issue does not name specific files or tests; locate the relevant implementations and tests, then check that the input stream uses the BufferAllocator and that both variants still work while reducing buffer allocation.

由索引模型根據 Issue 內容生成。

描述

help wanted

SnappyOutputStream uses a buffer management system to reduce memory pressure and GC overhead. The same mechanism would be helpful in SnappyInputStream as well.

We want to use Snappy for protocol compression in a high volume system. Currently we can see a significant increase in GC overhead due to the massive amount of buffers being allocated in SnappyInputStream. Adding the same BufferAllocator as in SnappyOutputStream would help to significantly reduce the amount of allocated memory.

Btw: we use both variants, the chunked one generated by SnappyOutputStream and the raw one used by a native Snappy implementation.

主要語言
Java
星號
1.1k
分支
261
平均合併
2 分鐘
30 天內合併 PR
2

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

xerial/snappy-java 的其他 Issue

查看 xerial/snappy-java 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。