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

Freqtrade cluster #252

Open
BigT-CZE opened this issue Oct 2, 2022 · 3 comments
Open

Freqtrade cluster #252

BigT-CZE opened this issue Oct 2, 2022 · 3 comments

Comments

@BigT-CZE
Copy link

BigT-CZE commented Oct 2, 2022

Hi, today in a new freqtrade version were introduced freqtrade clusters. Will you consider implementing this into your strategy? https://www.freqtrade.io/en/latest/producer-consumer/

@iterativv
Copy link
Owner

Hi. Sure thing, let me look into it first.

@DarkByteZero
Copy link

I would really like this implemented, running like 4 FreqTrade Instances with NFI is crazy intensive on the CPU.

@Toxiiin
Copy link

Toxiiin commented May 20, 2024

Did anybody already tried to use the consumer/producer logic? Thought about splitting the workload into a pipeline like:

flowchart TD
    A[Pairlist Producer] -->|Fetch global pairlist| B(OffsetFilter 0:20)
    A[Pairlist Producer] -->|Fetch global pairlist| C(OffsetFilter 21:40)
    A[Pairlist Producer] -->|Fetch global pairlist| D(OffsetFilter 41:60)
    A[Pairlist Producer] -->|Fetch global pairlist| E(OffsetFilter 61:80)

    B --> |Pairlist subset| F[Indicator Producer 0:20]
    C --> |Pairlist subset| G[Indicator Producer 21:40]
    D --> |Pairlist subset| H[Indicator Producer 41:60]
    E --> |Pairlist subset| I[Indicator Producer 61:80]
    
    F --> |Fetch indicators| J[Indicator Consumer]
    G --> |Fetch indicators| J[Indicator Consumer]
    H --> |Fetch indicators| J[Indicator Consumer]
    I --> |Fetch indicators| J[Indicator Consumer]
Loading

Any plans on integrating this (optionally)? Found some attempts on Discord, but nothing "official".

Had a small break, started again with my pi 4b to check current situation and recognized, that X4 is pretty much more computationally intensive than the version I used in '22 ... 😆 Everybody already switched to x86-64 or Pi 5 for whitelists with pairs >40?

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