Winservers.NET

StrategyQuant X · Real funnel

How Many Strategies Do You Need to Generate in StrategyQuant X?

Everyone who starts with StrategyQuant X asks the same thing: how many strategies must the Builder produce before something survives the robustness checks? Here is one honest answer from the logs of a real five-week run.

Quick answer: in our run 130.7 million generated strategies left 669 that passed every check. That is about one in 195,000, or roughly one final strategy per hour of server work. Your ratio depends on your filters, so use the method below to scale it.

The funnel

130.7 million in, 669 out

One dedicated server ran StrategyQuant X almost non-stop from August 4 to September 9, 2026. Fifteen project templates chained in an automated pipeline, genetic evolution, MetaTrader 5 engine, about 7 years of data, timeframes from M30 to H4. All counts come from the SQX project logs.

Generated and backtested by the Builder130,747,057
Every candidate the genetic search produced.
Accepted by the Builder filters374,397
0.29% of generated, 1 in 349.
Kept by the quality filter and sent to the OOS check66,691
17.8% of accepted. The Builder stops at 400 accepted strategies per run, then a quality filter keeps the better part.
Passed the OOS check51,061
76.6% of checked.
Kept for the heavy robustness checks7,270
14.2% of those that passed OOS, after a second quality filter.
Passed every check and reached final storage669
9.2% of those that entered the heavy checks, after all six checks and the last quality filter. 1 in 195,437 of all generated.
StageStrategiesShare of previous stageShare of all generated
Generated and backtested by the Builder130,747,057100.00%
Accepted by the Builder filters374,3970.29%0.2864%
Kept by the quality filter and sent to the OOS check66,69117.81%0.0510%
Passed the OOS check51,06176.56%0.0391%
Kept for the heavy robustness checks7,27014.24%0.0056%
Passed every check and reached final storage6699.20%0.0005%

What "final" means here: a strategy that passed the Builder filters, the quality filters between stages, OOS, Trade Manipulation, SPP, Randomize Data, Walk Forward and a tick retest. It says nothing about future profit. It only means the strategy survived the tests chosen for this project.

Stage 1

The Builder rejects 99.71% of what it generates

Most of the funnel is lost at the very first step, and that is by design: early filters are cheap, later checks are expensive. In this run the Builder accepted 374,397 strategies out of 130,747,057.

Why the Builder rejected a strategyShare of rejections
Net profit (OOS) is zero or negative20.2%
No trades18.9%
Did not get into the initial population16.9%
Too few trades13.2%
Trading months below 85% of the period11.7%
Open drawdown above 150% of in-sample10.4%
Many trades close on the same bar4.9%
Net profit (IS) is zero or negative2.4%
Yearly return at or below 3%1.1%
Otherunder 0.2%

If "no trades" and "too few trades" make up a third of your rejections, as they did here, the template is producing many dead candidates. Tightening the building blocks saves more time than faster hardware.

Acceptance by timeframe

Higher timeframes generate faster but accept a smaller share. Accepted strategies per hour is the number that matters for planning.

TimeframeStrategies generatedAccepted by BuilderAccepted %OddsAccepted per hour
M308,328,41654,0000.65%1 in 1541,116
H120,275,251153,6000.76%1 in 1322,666
H218,838,11385,4540.45%1 in 2203,067
H483,305,27781,3430.10%1 in 1,0241,433

Acceptance by trade direction

DirectionStrategies generatedAccepted by BuilderAccepted %OddsAccepted per hour
Long and short8,238,008117,6001.43%1 in 703,884
Long only34,357,650110,4010.32%1 in 3112,113
Short only88,151,399146,3960.17%1 in 6021,354

Long-and-short templates were the slowest to generate and the most productive: almost twice as many accepted strategies per hour as long-only, and nearly three times as many as short-only.

Stages 2 to 5

What the robustness checks remove

After the Builder, a quality filter kept 17.8% of accepted strategies for the OOS check, and a second one kept 14.2% of the OOS survivors for the heavy checks. Each individual check then passed about 77% to 85% of what it tested.

CheckStrategies checkedPassedPass rateHoursSeconds per strategy
OOS (out of sample)66,69151,06176.6%3.20.2
Trade Manipulation7,2706,18685.1%0.60.3
SPP (System Parameter Permutation)6,9365,69982.2%75.739
Randomize Data (Monte Carlo)6,9005,57480.8%260.2136
Walk Forward5,5064,59483.4%149.698
Tick Retest5,7294,58980.1%12.67.9

The checks are not strict one after another in the logs, so read the pass rates per check, not as a chain. Counts are passed plus failed, because the Total field in the SQX retest logs is not filled correctly.

Where the time goes: generation took 190.6 hours, the checks 501.8 hours. Randomize Data and Walk Forward alone took about 410 hours for fewer than 7,000 strategies each. The funnel is narrow at the top and expensive at the bottom. See how long Walk Forward and Monte Carlo take.

Your turn

How to plan your own run

  1. Measure your acceptance rate. Open user\projects\<your project>\log\global_log_*.log and read the Builder line: Strategies generated, Accepted and Accepted strategies per hour.
  2. Measure your survival rate. Count how many strategies reach your final databank after all checks and divide by the number accepted by the Builder. In our run it was 669 of 374,397, or 0.18%.
  3. Multiply. Strategies to generate = final strategies you want ÷ acceptance rate ÷ survival rate.
  4. Add the checks. Multiply the number of strategies entering each heavy check by its seconds per strategy. This part usually decides the calendar time.

With the ratios from this run, on the same server, the plan looks like this:

Final strategies you wantStrategies to generateBuilder timeAll work, with checksCalendar time at 80% load
101,954,3703 h10 h0.5 days
509,771,85014 h52 h2.7 days
10019,543,70028 h103 h5.4 days
50097,718,500142 h517 h26.9 days

These rows scale our own ratios. They are a reference for the order of magnitude, not a promise for your project: other filters, another template or tick precision in the Builder will change every column.

Good ways to widen the funnel

  • Remove building blocks that produce strategies with no trades.
  • Run the first pass on a higher timeframe or shorter history.
  • Keep cheap filters early and expensive checks late.
  • Let heavy checks run on a server that works for days.

Ways that only look faster

  • Loosening robustness checks until more strategies pass.
  • Comparing strategies per hour between different templates.
  • Judging hardware by the Builder only and ignoring Walk Forward time.
  • Sharing one machine between SQX research and live terminals.

Hardware

What this means for the server

The run used an Intel Core i9-13900 server with 16 threads in use, 64 GB DDR5 and NVMe storage. It produced about 19 final strategies per day at 80% load. Two things follow. First, a funnel this narrow needs a machine that can work for weeks without being switched off or shared. Second, since checks take 70% of the time, size the server for Walk Forward and Monte Carlo, not only for generation speed.

Speed by timeframe, time per check and a way to compare with your PC are in the StrategyQuant X benchmark. For VPS or dedicated, recommended CPU, RAM and NVMe and current prices, see StrategyQuant X Server: VPS or Dedicated? and StrategyQuant X system requirements and the dedicated servers page.

Ask which server fits my SQX project

FAQ

Frequently asked questions

How many strategies do I need to generate in StrategyQuant X?

It depends on your filters. In our five-week run 130.7 million generated strategies gave 669 that passed every robustness check, about one in 195,000. With looser filters you need fewer, with stricter filters more. Use your own acceptance rate from the Builder log to scale the estimate.

What is a normal acceptance rate in the StrategyQuant X Builder?

In this run the Builder accepted 0.29% of generated strategies on average. By template it ranged from 0.06% for H4 short-only to 2.27% for H1 long-and-short. The rate is set by your filters, not by hardware.

How long does it take to get one robust strategy?

On this server, about one hour of work per strategy that passed every check: 692 working hours for 669 strategies. Most of that time went to Randomize Data and Walk Forward checks, not to generation.

Does a strategy that passes all checks make money?

No guarantee. Robustness checks only show that a strategy survived the tests you chose on historical data. They do not predict live results. Winservers.NET rents servers and does not give trading advice.

Which stage removes the most strategies?

The Builder filters. They rejected 99.71% of everything generated. The most common reasons were zero or negative out-of-sample profit, no trades and too few trades.

How can I get more strategies through the funnel in the same time?

Use a higher timeframe or a shorter history for the first pass, keep early filters cheap, and give the heavy checks to a server that can run for days. More CPU threads shorten generation and checks alike.

Planning a long StrategyQuant X run?

Send us your timeframe, data period, filters and the checks you use. We will suggest a dedicated server and tell you what to expect from it.

Ask in WhatsApp or Telegram

K.S.M. Trade Sp. z.o.o. | NIP/VAT PL5273128546 | REGON 52957272900000 | Warsaw, Poland