GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • PineForgePF
  • Methodology
  • Compare
  • Gallery
  • AI assistants
  • Pricing
  • FAQ
  • Blog
  • Backtest offline
  • Backtest in CI
  • For teams
  • Sell strategies
  • Sell Pine as a binary
  • Why PineForge

This view

  • Original page
  • New address

GeezerVison is showing pineforge.dev — Your Pine strategy, compiled. TradingView’s trades, reproduced.

Join the waitlist

You get one welcome email now. Reply STOP to any email to unsubscribe.

Pine Script backtest: 11,800 trades. Not one differs.

7,989 backtests graded, 100.00 % excellent or strong

Trade
11,800
TradingView
262.81
PineForge
262.81
Trade 4,100 longEntryExitNet P&L, USDTTradingView4,306.954,296.64−10.31PineForge4,306.954,296.64−10.31
Market
ETHUSDT.P
Timeframe
15-minute
Graded
1,009
Excellent
1,009
Strong
0
Speed-up
36×
Rank
101
01,0002,000
02,0004,0006,0008,00010,000
USDT

Tap or drag the chart to read any point.

Source: probe composite-vcp-fvg-active-zones-01, pineforge-corpus d75b4fa, 2025-03-31 to 2026-05-01: CSV files, gallery page.

The chart as a table
TradeTradingView, USDTPineForge, USDT
00.000.00
1,4701,080.011,080.01
2,953702.71702.71
4,4352,009.592,009.59
5,9101,726.021,726.02
7,3751,349.791,349.79
8,858883.15883.15
10,341458.12458.12
11,800262.81262.81
The chart as a table

48 consecutive trades of the same strategy on the 178 Binance ETHUSDT perpetual 15-minute candles around them. TradingView’s export and PineForge’s trade book agree on side, entry and exit time, entry and exit price and net P&L, row for row.

TradeSideEntry, TradingViewEntry, PineForgeExit, TradingViewExit, PineForgeNet P&L, TradingViewNet P&L, PineForge
4,100long4,306.954,306.954,296.644,296.64−10.31−10.31
4,106long4,279.174,279.174,276.804,276.80−2.37−2.37
4,112long4,327.734,327.734,315.744,315.74−11.99−11.99
4,118long4,272.714,272.714,242.194,242.19−30.52−30.52
4,124long4,779.504,779.504,760.734,760.73−18.77−18.77
4,129long4,749.874,749.874,738.934,738.93−10.94−10.94
4,135long4,718.894,718.894,731.004,731.0012.1112.11
4,141long4,723.344,723.344,718.714,718.71−4.63−4.63
4,147long4,752.764,752.764,745.124,745.12−7.64−7.64
The chart as a table

Each mark is one strategy script on one market and timeframe; the 6 amber ones graded strong, the other 7,983 excellent.

MarketTimeframeGradedExcellentStrong
ETHUSDT.P15-minute1,0091,0090
BTCUSDT15-minute6686662
BTCUSDTDaily5165160
ETHUSDT.PDaily5405400
Other15-minute3,0813,0774
OtherDaily2,1752,1750
The chart as a table

Each mark is one of the 200 strategies timed on both engines, at its exact speed-up on a log scale.

RankSpeed-up
12.5×
2621×
5126.2×
7631.2×
10136×
12547.4×
15055.3×
17571.5×
2001,307×
How this is measured

100.00 % of 7,989 graded backtests are excellent or strong against TradingView’s own trade lists, and the median run is 36× faster than PyneCore (how we timed it).

Main baseline 2026-11-03, engine 59f98ba8. Release v1.10.0: 7,983 excellent, 6 strong. Methodology

Probe composite-vcp-fvg-active-zones-01 in pineforge-corpus at commit d75b4fa: Binance ETHUSDT perpetual, 15-minute bars, 2025-03-31 to 2026-05-01. PineForge’s trade list there was written on 2026-10-02 by engine v1.0.1. See the CSV files or open it in the gallery.

How we timed it: PineForge in-process with Google Benchmark, bar magnifier on; PyneCore 6.10.3 as a subprocess, so its wall time includes interpreter start-up. An AWS c7a.8xlarge (AMD EPYC 9R14, 32 cores, SMT off) running Ubuntu 24.04, each timing process pinned to fixed cores; engine 35db01c8, 2026-09-29, one 53,929-bar ETHUSDT 15-minute feed. Engine v1.10.0 was released after it, and the timings were not re-measured on the release. Read the full benchmark.

Run it where your strategy lives

PineForge’s own C++ engine runs PineScript v6: offline, in CI or from your AI agent.

  1. Hosted MCP

    claude mcp add --transport http pineforge https://mcp.pineforge.dev/mcp

    Another MCP client? See its setup.

  2. Docker

    Runs the released engine on your OHLCV file; your data stays local. Offline guide.

    docker run --rm --network=none \
      -v "$PWD/strategy.pine:/in/strategy.pine:ro" \
      -v "$PWD/ohlcv.csv:/in/ohlcv.csv:ro" \
      ghcr.io/pineforge-4pass/pineforge-release:1.10.0 > report.json

  3. Source

    Open pineforge-engine on GitHub

Strategy-pool optimization and a hosted Studio are planned. We’ll email you when each one opens.

You get one welcome email now. Reply STOP to any email to unsubscribe.

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.