Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Langgraph process uses always 100% CPU #227

Open
tisDDM opened this issue Jan 4, 2025 · 4 comments
Open

Langgraph process uses always 100% CPU #227

tisDDM opened this issue Jan 4, 2025 · 4 comments

Comments

@tisDDM
Copy link

tisDDM commented Jan 4, 2025

When I start up the Dev-Server with langgraph up or start the docker manually the server process always speeds up to 100% usage (one core).

Has anyone encountered similiar? Any known solutions?

@marc-hughes
Copy link

I also experience this while running langgraph up --watch --port 54367 inside an ubuntu based WSL on Windows 11.

@TomTom101
Copy link

Same, it then crashes after a while

@bracesproul
Copy link
Member

Hi @tisDDM @marc-hughes @TomTom101 we recently released an in memory server for LangGraph.js which is now the recommended method for running LangGraph.js locally for testing/development.

You can use the in mem server by running the yarn dev:server script!

@tisDDM
Copy link
Author

tisDDM commented Jan 28, 2025

Hi @bracesproul ,

Thank you for your work in this project and your comment to the issue.

I stopped working with your canvas - which is a very great idea indeed. But there are reasons why I do not put any effort into using it.

  1. The canvas itself is open source and under an open license. But langgraph isn't. Hard to run it w/o legal issues. And why should I just take part in developing without using?
  2. Supabase is annoying. Why is the authentication (and more) part of the project, especially in this way? Normally this shall be handled in an other instance of the infrastructure. Furthermore they sent annoying advertisements. It stopped when the hibernated my account due to 6 days(!!!!) of inactivity. Great.
  3. Code quality could be a lot improved. Found tons of hardcoded stuff, that needed fixing for use in a multi-container environment. Not talking about the strange hassle when implementing new LLMs
  4. Even langgraph runs unstable at least locally. Its hard and unintuitive to work with this product.

I am a very experienced developer and I spent a few month in the langchain universe.

I already have quit and be heading in direction of CrewAI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants