How to Optimize Pine Script Code for Speed and Memory Limits

Common performance bottlenecks in TradingView scripts

TradingView executes Pine Scripts inside a sandboxed environment with strict resource constraints. A script that runs smoothly on a 1D chart with 500 bars can crash with "Script calculation takes too long" on a 1-minute chart spanning 20,000 historical bars. Recognizing where scripts consume memory and CPU cycles allows you to preempt performance degradation.

Before & after code example: Replacing a slow historical loop with rolling math

Here is a direct comparison showing how to replace an unoptimized nested for-loop with an efficient O(1) rolling calculation in Pine Script v6.

//@version=6
indicator("Loop Optimization Demo [v6]", overlay = false)

period = input.int(100, "Lookback Period")

// SLOW APPROACH (O(N) operations per bar):
// float slowSum = 0.0
// for i = 0 to period - 1
//     slowSum += volume[i]

// FAST APPROACH (O(1) constant time rolling sum):
// Built-in ta.cum() or ta.sma() calculates in compiled C++
fastSum = ta.sma(volume, period) * period

plot(fastSum, "Optimized Rolling Volume Sum", color = color.teal)

Drawing object management: Lines, boxes, and labels

TradingView restricts the maximum active drawing objects (lines, boxes, labels) to 500 per script. If your script draws support lines or signal tags without cleanup, old drawings are silently dropped or the script crashes with RE10139 errors. Follow these rules for drawings:

• Set max_bars_back and max_lines_back explicitly: Inside indicator() or strategy(), declare max_lines_back = 100, max_labels_back = 100 to allocate memory buffers accurately.
• Use circular drawing arrays: Store drawing IDs in an array. When array.size(lineArray) >= maxAllowed, call line.delete(array.shift(lineArray)) before adding the new drawing ID.
• Prefer plot() over line.new() where possible: plot() is handled natively by the chart rendering engine and consumes significantly fewer resources than dynamic drawing objects.

//@version=6
indicator("Clean Drawing Buffer [v6]", overlay = true, max_lines_back = 50)

var line[] lineBuffer = array.new_line()
maxLines = 10

if ta.crossover(close, ta.sma(close, 20))
    // Create new support line
    newLine = line.new(bar_index - 5, close, bar_index, close, color = color.green, width = 2)
    array.push(lineBuffer, newLine)
    
    // Maintain maximum active lines
    if array.size(lineBuffer) > maxLines
        oldestLine = array.shift(lineBuffer)
        line.delete(oldestLine)

Overcoming "Calculation takes too long" and recursion errors

TradingView terminates any script execution that exceeds a predetermined CPU execution time (typically 20–40 milliseconds per calculation tick). If your script triggers this warning:

• Guard heavy calculations with barstate.islast or barstate.isconfirmed: If a visual dashboard or table only needs to show current data, calculate it only on the last bar: if barstate.islast.
• Avoid self-referencing recursive definitions across long histories: Pine Script evaluates historical depth lazily. Use explicit var accumulators instead of deep recursive indexing like myVal[1].
• Break out of loops early: In search loops (e.g. scanning for previous pivot points), insert break statements as soon as the target condition is satisfied.