dgraph-io / dgraph-io/badger

Memory Fluctuation Issue When using Jaeger with Badger

Open
#2,190 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Stale
Dominant language
Go
Stars
15.8k
Forks
1.3k
Avg merge
2m
Merged PRs (30d)
1

Description

Description
When using Badger, I've encountered a problem where there is a noticeable memory fluctuation approximately every few hours. As shown in the attached graph [insert graph link if applicable], the memory usage spikes at regular intervals, which may impact the performance and stability of the application using Badger.

Image

Steps to Reproduce
Set up a Badger - based application with a workload that runs continuously.
Monitor the memory usage over time using a memory profiling tool (e.g., [mention the tool used]).
Observe that the memory usage will experience significant fluctuations every few hours.
Expected Behavior
Memory usage should remain stable or within a predictable range, without these periodic large - scale fluctuations, to ensure consistent application performance.
Actual Behavior
Memory usage shows sharp spikes at intervals of a few hours, causing potential instability in the application. This may lead to performance degradation, increased latency, or even application crashes under heavy load.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files, tests, entry points, profiling tool, workload, or usable graph link are identified. Start by reproducing the issue in a continuously running Badger-based application with Jaeger enabled and capture memory profiles; done means the periodic fluctuation is explained and a verified fix or narrowed cause is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
databases, observability
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.