mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-21 17:45:23 -04:00
High CPU usage (100%) when sending images with OpenAI plugin v0.0.16+ #209
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sakuranaga on GitHub (Apr 19, 2025).
Originally assigned to: @Yeuoly on GitHub.
Self Checks
Dify version
1.2.0
Plugin version
0.0.19
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
Description
After upgrading the OpenAI plugin to version 0.0.16 or above, sending an image causes the Gunicorn worker process to spike to 100% CPU usage and the request fails to complete. This issue does not occur with version 0.0.15.
Steps to Reproduce
Build and run the service in Docker:
bash
docker compose up -d
Use the plugin to send any image payload to the API endpoint.
Monitor CPU usage via top or similar tool.
Expected Behavior
CPU usage should remain within normal bounds (e.g. below 50%) and the image request should be processed successfully, as observed in v0.0.15.
Actual Behavior
Gunicorn worker CPU usage jumps to 100%.
System load average increases sharply.
The request hangs or fails due to CPU saturation.
Environment
difify version: 1.2.0
OpenAI plugin version: 0.0.16 (and above)
Server OS: Ubuntu 24.04.2 LTS
Docker version: 28.1.1, build 4eba377
Deployment: Docker Compose
Additional Notes
Downgrading the plugin to v0.0.15 immediately resolves the issue, confirming a regression in v0.0.16.
✔️ Error log
No response
@kurokobo commented on GitHub (Apr 19, 2025):
Related to: https://github.com/langgenius/dify/issues/17799
Your problem should be partly resolved when the next release of Dify comes out, the next release of the Plugin SDK is released, and the OpenAI plugin starts using the new Plugin SDK.