alibaba / alibaba/Sentinel

Sentinel performance footprint, leading to frequent YGC

Open
#1,563 10 comments 3 reactions 0 assignees View on GitHub
area/performance
Dominant language
Java
Stars
23.1k
Forks
8.1k
PR merge metrics
No merged PRs in 30d

Description

我用的网关是Gateway ,在没有集成Sentinel之前 ,一切正常。
但是 集成了Sentinel之后 ,发现YGC的次数每天都在增长
比如刚启动的时候 一天YGC是24次,第二天就变成了26次,第三天就变成了28次,第四天就是30次
然后就越来越频繁。总之呢就是年轻代被填满的速度越来越快。最后监控jvm的GC图填满整个年轻代几乎成了一条细线。STW次数越来越多,严重影响性能。希望能解决一下。
集成之前

![gsberofr](https://user-images.githubusercontent.com/45376648/85187256-dc77c580-b2d0-11ea-8951-cd15166666b2.png)
集成之后
![gsmiddle](https://user-images.githubusercontent.com/45376648/85187266-e7325a80-b2d0-11ea-8db1-91c899593af1.png)
再往后
![gs3rd](https://user-images.githubusercontent.com/45376648/85187270-f1ecef80-b2d0-11ea-9d6f-6d13962f2056.png)
继续观察
![gs4rd](https://user-images.githubusercontent.com/45376648/85187277-fe714800-b2d0-11ea-98ef-3a602c6d1ea2.png)
最后
![gs5rd](https://user-images.githubusercontent.com/45376648/85187299-28c30580-b2d1-11ea-9513-193ac0029caf.png)

Contributor guide

Open the contributing guide

Research direction

The report compares Gateway behavior before and after Sentinel integration and includes JVM YGC and STW monitoring screenshots. Start by reviewing those comparisons and the Sentinel integration context; no file, test, or entry point is named. Done means establishing a reproducible cause for the increasing young-generation collection frequency and confirming improved performance.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.