Issue Station
Sign In
Tools hereToolbox

dify - 💡(How to fix) Fix very high gpu utility with chrome [4 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
langgenius/dify#35638•Fetched 2026-04-29 06:36:23
View on GitHub
Comments
4
Participants
2
Timeline
5
Reactions
1
Author
shesungshesung
Participants
PHclawPHclawshesungshesung
Timeline (top)
commented ×4labeled ×1
RAW_BUFFERClick to expand / collapse

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.13.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Running a simple workflow with LLM in chrome, M1pro's gpu goes to 100%, and system power raise rapidly. With the same page running in safari, gpu utility is much lower.

✔️ Expected Behavior

The workload for web rendering should not go so high.

❌ Actual Behavior

No response

extent analysis

TL;DR

The issue might be related to browser-specific rendering differences, and switching to a different browser like Safari already shows a lower GPU utility.

Guidance

  • Investigate browser-specific optimizations for Chrome to reduce GPU usage.
  • Compare Chrome and Safari's rendering settings and extensions to identify potential differences.
  • Consider testing the workflow with other browsers to see if the issue is Chrome-specific.
  • Review the system's power management settings to ensure they are not contributing to the rapid power increase.

Notes

The issue seems to be related to browser-specific behavior, and more information about the system's configuration and the specific workflow being run would be helpful to provide a more detailed solution.

Recommendation

Apply workaround: Test the workflow with different browsers and configurations to identify the root cause and potential optimizations.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#batch processing#GPU compatibility#latency issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

dify - 💡(How to fix) Fix very high gpu utility with chrome [4 comments, 2 participants]