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

Behaviour of processpool #237

Open
raphael-bresson opened this issue Nov 17, 2023 · 1 comment
Open

Behaviour of processpool #237

raphael-bresson opened this issue Nov 17, 2023 · 1 comment

Comments

@raphael-bresson
Copy link

Hi I'm developing a web app with

  • Flask + Flask_APScheduler + Flask_SocketIO on the server side
  • VueJS on the front side.

I encounter several issue on the server side when using a process pool instead of a thread pool to run my background tasks (heavy):

  1. The socketIO.emit calls from my jobs are not always sent to my client. Sometimes yes, others no. Not sure why.

  2. The auto reload feature of Flask seems broken. It is stuck because of the background process not properly killed I suppose. But I know that it ended normally.

None of this behaviors happen with a thread pool.

Could any of you help me on that ?

Thanks

@viniciuschiele
Copy link
Owner

Hi,

I can try to investigate this further if you can provide a repository that reproduces the issue

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

2 participants