Winservers.NET

StrategyQuant X · Real benchmark

StrategyQuant X Benchmark: Strategies per Hour on a Real Server

How fast should StrategyQuant X be? Vendors rarely publish numbers, so here are ours: five weeks of real strategy generation and robustness checks on one dedicated server, taken straight from the logs SQX writes by itself.

Quick answer: on an Intel Core i9-13900 server with 16 threads and 7 years of data, StrategyQuant X generated about 172,000 strategies per hour on M30, 352,000 on H1, 676,000 on H2 and 1,467,000 on H4. A Walk Forward check took about 98 seconds per strategy and Randomize Data about 136 seconds.

Main numbers

Five weeks of StrategyQuant X on one server

The server ran from August 4 to September 9, 2026. Fifteen projects started each other in a chain (how the pipeline works). Every number on this page is calculated from the SQX project logs (global_log_*.log), 11,778 logged tasks in total.

130.7Mstrategies generated and tested
686,000strategies per hour on average, peak 3.2 million
692 hof work in 860 calendar hours, about 80% load
669strategies passed every check
ResultValue
Strategies generated and tested130,747,057
Accepted by the Builder filters374,397 (0.29%)
Builder runs944
Time spent on generation (Build)190.6 hours
Time spent on robustness checks (Retest)501.8 hours
Average generation speed (all generated / all Build time)686,000 per hour
Median speed across Builder runs487,000 per hour
Peak speed in one run3,198,886 per hour
Median time per strategy7 ms
Average per dayabout 3.6 million strategies
Reached final storage after all checks669 strategies

Test setup

Server and workload

Server

  • Intel Core i9-13900 (Raptor Lake), L2 16 MB, L3 36 MB
  • 16 threads visible to Windows and SQX: 8 performance cores with Hyper-Threading. All results are for these 16 threads.
  • 64 GB DDR5-4800 (2 × 32 GB)
  • 2 × 1.92 TB NVMe SSD, Samsung PM9A3
  • Windows Server 2019 Standard
  • StrategyQuant X build 144, Java heap -Xmx56g, ParallelGC
  • SQX used 15 threads, one was left to the system

Workload

  • Genetic evolution, population 200
  • MetaTrader 5 backtest engine (hedged)
  • About 7 years of data, October 2017 to October 2024, with in-sample and two out-of-sample parts
  • Builder on M1 base precision, tick check as a separate stage
  • Timeframes M30, H1, H2, H4
  • Long only, short only, long and short
  • Forex, metals and index CFDs
  • 29 instruments of tick and M1 history on disk, about 92 GB

The cycle of every project: Build, OOS, Trade Manipulation, SPP, Randomize Data, Walk Forward, Tick Retest, Final Storage, then restart. During the whole run SQX had 56 GB of heap and never ran out of memory.

Generation speed

Strategies per hour by timeframe

Timeframe is the main factor. A higher timeframe has fewer bars, so each backtest is shorter. On the same 7 years of data M30 was about 8.5 times slower than H4. This is the table to compare with your own machine.

TimeframeBuilder runsStrategies generatedAcceptedAccepted %Build hoursStrategies per hourAccepted per hour
M301358,328,41654,0000.65%48.4172,0001,116
H138720,275,251153,6000.76%57.6352,0002,666
H221418,838,11385,4540.45%27.9676,0003,067
H420883,305,27781,3430.10%56.81,467,0001,433
All944130,747,057374,3970.29%190.6686,0001,964

By trade direction

One-sided templates are rejected by early filters more often (for example, no trades), so generation runs faster and the share of accepted strategies is lower.

DirectionBuilder runsStrategies generatedAcceptedAccepted %Build hoursStrategies per hourAccepted per hour
Long and short2998,238,008117,6001.43%30.3272,0003,884
Long only27734,357,650110,4010.32%52.2658,0002,113
Short only36888,151,399146,3960.17%108.1815,0001,354

By exit type

Exit typeBuilder runsStrategies generatedAcceptedAccepted %Build hoursStrategies per hourAccepted per hour
Exit at end of day31718,071,982126,0000.70%76.0238,0001,658
Exit at end of Friday627112,675,075248,3970.22%114.6983,0002,167

By project template

All 15 templates, speed calculated as strategies generated divided by Build hours.

TemplateBuilder runsStrategies generatedAcceptedAccepted %Build hoursStrategies per hourAccepted per hour
M30, long and short, end of day exit431,865,98017,2000.92%13.8135,0001,243
M30, long only, end of day exit383,121,92815,2000.49%17.3181,000879
M30, short only, end of day exit543,340,50821,6000.65%17.3194,0001,252
H1, long and short, end of day exit602,117,40523,2001.10%8.0264,0002,890
H1, long and short, end of Friday exit651,147,03926,0002.27%4.2276,0006,246
H1, long only, end of day exit512,726,23420,4000.75%6.9393,0002,943
H1, long only, end of Friday exit712,958,98528,0000.95%7.8377,0003,570
H1, short only, end of day exit714,899,92728,4000.58%12.6388,0002,247
H1, short only, end of Friday exit696,425,66127,6000.43%18.0357,0001,533
H2, long and short, end of Friday exit651,366,18726,0001.90%2.6527,00010,035
H2, long only, end of Friday exit634,504,65925,2000.56%6.0745,0004,169
H2, short only, end of Friday exit8612,967,26734,2540.26%19.2674,0001,781
H4, long and short, end of Friday exit661,741,39725,2001.45%1.71,051,00015,216
H4, long only, end of Friday exit5421,045,84421,6010.10%14.11,489,0001,529
H4, short only, end of Friday exit8860,518,03634,5420.06%41.01,477,000843

How long one Builder run lasted

Shortest25% of runs shorter thanMedian75% of runs shorter thanLongest
under 1 min1.8 min4.2 min10.6 min4 h 23 min

Robustness checks

Time per strategy in each check

In practice most of the time goes to heavy checks, not to generation. Generation took 190.6 hours, the checks 501.8 hours. Randomize Data and Walk Forward alone used about 410 hours. If you run many checks like these, compare servers by them first. See how long Walk Forward and Monte Carlo take.

CheckStrategies checkedPassedPassed %HoursSeconds per strategyStrategies per hour
OOS (out of sample)66,69151,06176.6%3.20.220,800
Trade Manipulation7,2706,18685.1%0.60.312,100
Tick Retest5,7294,58980.1%12.67.9456
SPP (System Parameter Permutation)6,9365,69982.2%75.73992
Walk Forward5,5064,59483.4%149.69837
Randomize Data (Monte Carlo)6,9005,57480.8%260.213627

The number of checked strategies is counted as passed plus failed, because the Total field in the SQX retest logs is not filled correctly.

Your turn

How to compare with your own PC or server

  1. Open the folder user\projects\<your project>\log\ in your StrategyQuant X installation.
  2. Open the newest global_log_*.log and find the line written after a Builder task:
Strategies generated: 18524, Time per strategy: 3 ms., ... Strategies per hour: 1008109, Accepted strategies per hour: 21769
  1. Compare Strategies per hour with the timeframe table above. Use a project with a similar data period (about 7 years) and similar backtest precision.
  2. For checks, find the line with Time per strategy after an AutomaticRetest task and compare it with the checks table.

What changes the number

Timeframe and history length

M30 was 8 to 9 times slower than H4 here. Twice the history means roughly twice the bars to test.

Backtest precision

The Builder here used M1 base precision. Tick precision in the Builder would be much slower; in this pipeline the tick check ran as a separate stage.

Template complexity

More entry and exit conditions, more indicators and multi-timeframe logic all add work per strategy.

How early filters reject

The earlier a strategy is thrown away, the higher the strategies per hour. A high number can mean fast hardware or strict early filters.

Compare like with like. Strategies per hour is not a pure hardware number. On this one server templates ranged from about 135,000 to 1,489,000 strategies per hour. Seconds per strategy in Walk Forward and Randomize Data is the steadier figure for comparing machines.

Reference data

Load by week, rejection reasons and an earlier run

Load by week

In weeks with few Build hours the server was busy with retests: Randomize Data, Walk Forward and SPP.

Week starting (2026)Builder runsStrategies generatedAcceptedBuild hours
August 323712,432,08792,54314.2
August 107531,983,67930,00039.8
August 1728841,159,870115,05454.5
August 241064,911,77742,4008.7
August 3120438,351,92781,60065.7
September 7341,907,71712,8007.8

Why the Builder rejected strategies

With this set of filters you can estimate how many strategies you need to generate to get a given number of candidates. In this run 0.29% of generated strategies were accepted. The full path from 130.7 million generated to 669 final strategies is in How many strategies do you need to generate?

Rejection reason in the BuilderShare
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%

Earlier run on the same server

June 2026, StrategyQuant X build 143, different templates. The spread shows how much the template matters on identical hardware.

Template (SQX build 143)Builder runsStrategies generatedAcceptedBuild hoursStrategies per hour
Trend template83,681,6445,88713.6270,000
Mean reversion template83,329,8524,4451.22,680,000

What it means

Choosing a server for StrategyQuant X

Generation speed sells a server, but checks decide how long your research takes. In this run one strategy needed about 98 seconds of Walk Forward and 136 seconds of Randomize Data, so a few thousand candidates already mean days of work. Size the server for the checks you run, not only for the Builder.

For the difference between a VPS and a dedicated server, recommended CPU, RAM and NVMe ranges and current prices, see StrategyQuant X Server: VPS or Dedicated? and StrategyQuant X system requirements. License and hardware budget: how much StrategyQuant X costs. Servers and prices are on the dedicated servers page. If your bottleneck is the MT5 Strategy Tester rather than SQX, look at the MT5 optimization server and the MT5 backtest farm.

Ask which server fits my SQX project

FAQ

Frequently asked questions

How many strategies per hour is normal in StrategyQuant X?

There is no single normal number. On the same server with 7 years of data we measured about 172,000 strategies per hour on M30, 352,000 on H1, 676,000 on H2 and 1,467,000 on H4. Template complexity, history length, backtest precision and filters change the result several times over, so compare only similar projects.

Where do I find Strategies per hour in StrategyQuant X?

Open the folder user\projects\your project\log\ in the StrategyQuant X installation and open the newest global_log file. After each Builder task SQX writes a line with Strategies generated, Time per strategy, Strategies per hour and Accepted strategies per hour.

Why is M30 so much slower than H4?

A lower timeframe has more bars for the same period, so every backtest does more work. In this run M30 was about 8.5 times slower than H4 on the same 7 years of data.

Which StrategyQuant X check takes the longest?

In this workload Randomize Data took about 136 seconds per strategy and Walk Forward about 98 seconds. Together they used about 410 of 692 working hours, more than strategy generation itself.

Is this a synthetic benchmark?

No. The numbers come from the project logs of a real five-week research run: 944 Builder runs and the full chain of robustness checks on one dedicated server. Nothing was tuned for the test.

Can I get a server like this for StrategyQuant X?

Yes. Winservers.NET rents dedicated servers with Windows Server and Remote Desktop for StrategyQuant X research. Tell us your timeframe, data period and the checks you run, and we will suggest a configuration.

Want these numbers for your own project?

Send us your timeframe, data period and the checks you run. We will suggest a dedicated server for StrategyQuant X 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