CTYPTO/freqtrade
1
0
Fork 0
mirror of https://github.com/freqtrade/freqtrade.git synced 2026-01-26 08:50:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

Deployed 81b4285 to develop in en with MkDocs 1.6.1 and mike 2.1.3

Browse Source
This commit is contained in:
github-actions[bot]
2025-01-20 18:23:33 +00:00
parent 72d1724a02
commit aa179094fc
2 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
en/develop/search/search_index.json
View File

File diff suppressed because one or more lines are too long

12
en/develop/strategy-callbacks/index.html
View File

@@ -2934,6 +2934,12 @@ Adjustment orders can be assigned with a tag by returning a 2 element Tuple, wit
<p>Same thing also can happen with partial exit. So be sure to have a strict logic and/or check for the last filled order.</p>
</div>
<div class="admonition warning">
<p class="admonition-title">Performance with many position adjustments</p>
<p>Position adjustments can be a good approach to increase a strategy's output - but it can also have drawbacks if using this feature extensively.<br />
Each of the orders will be attached to the trade object for the duration of the trade - hence increasing memory usage.
Trades with long duration and 10s or even 100ds of position adjustments are therefore not recommended, and should be closed at regular intervals to not affect performance.</p>
</div>
<div class="admonition warning">
<p class="admonition-title">Backtesting</p>
<p>During backtesting this callback is called for each candle in <code>timeframe</code> or <code>timeframe_detail</code>, so run-time performance will be affected.
This can also cause deviating results between live and backtesting, since backtesting can adjust the trade only once per candle, whereas live could adjust the trade multiple times per candle.</p>
@@ -2962,12 +2968,6 @@ Returning a value more than the above (so remaining stake_amount would become ne
Regular stoploss rules still apply (cannot move down).</p>
<p>While <code>/stopentry</code> command stops the bot from entering new trades, the position adjustment feature will continue buying new orders on existing trades.</p>
</div>
<div class="admonition warning">
<p class="admonition-title">Performance with many position adjustments</p>
<p>Position adjustments can be a good approach to increase a strategy's output - but it can also have drawbacks if using this feature extensively.<br />
Each of the orders will be attached to the trade object for the duration of the trade - hence increasing memory usage.
Trades with long duration and 10s or even 100ds of position adjustments are therefore not recommended, and should be closed at regular intervals to not affect performance.</p>
</div>
<div class="highlight"><pre><span></span><code><span class="c1"># Default imports</span>
<span class="k">class</span><span class="w"> </span><span class="nc">DigDeeperStrategy</span><span class="p">(</span><span class="n">IStrategy</span><span class="p">):</span>