r/metatrader

▲ 6 r/metatrader+1 crossposts

I do not see the effects of leverage

Can someone tell me why I can never see any difference when I change leverage sizes.
I went from 1:100 to 1:500 but I did not see any difference in margin size or pip size
Or even margin size.
You would think that the price of margin per 0.01 would change when one switches up or down leverage size.

But I never see any difference.
Not even the equity size changes.

Where am I looking wrong?

I trade oil with one broker I pay 4USD and with another its around 1USD. I cant change that size with leverage to make it affordable or otherwise.
And the pip sizes seems to be 0.10cents with one broker and much more with another.

What is your leverage size and or what is your type of account.

What differences do you see?
Please divulge

reddit.com
u/MuchoPaper — 5 days ago
▲ 27 r/metatrader+1 crossposts

Coded an extensive EA that has 10 engines and also has a control panel

10 engines all different strategies and logic all working together and alone , swing trades , a control panel that u can view all pairs turn them on/off adjust risk for all

u/shankil_weru — 6 days ago
▲ 3 r/metatrader+1 crossposts

i tested 13 strategies on 2 years of gold and nasdaq futures data. only 3 survived

been building trading bots for a while and got tired of strategies that look good on a chart and die live. so i ran 13 common setups through 2 years of data with real costs.

10 failed. the 3 that held up:
gold pullback after the opening range, profit factor 1.52
gold afternoon trend, profit factor 1.40
nasdaq prior day breakout, profit factor 1.46

biggest lesson: most "high win rate" setups lost money once you add slippage and fees. the ones that survived win around half the time but make more on wins than they lose.

happy to answer questions on how i tested them
reddit.com
u/jtxcode — 3 days ago

Cloud-based MT4/MT5 Trade Copier (Headless, No VPS) — Looking for beta testers & stress-testing

TL;DR: I built a headless MT4/MT5 cloud copier that connects directly at the protocol level (zero VPS or desktop terminal instances required) and scales to 2,000+ concurrent operations. Looking for multi-account traders to help stress-test broker-specific routing edge cases on demo.

Hey everyone,

I’m a backend engineer working on custom MT4/MT5 infrastructure. I built SnapCopier, a cloud-based copier engine designed for high concurrency without running multiple desktop terminals or VPS instances.

Instead of automating desktop GUI clients via local files or DLLs, accounts connect headlessly at the network protocol level, completely bypassing MQL thread locks and Windows resource bloat.

Concurrency & Benchmark Numbers

During recent stress testing with 95 connected accounts simultaneously closing 26 open trades each (~2,470 concurrent operations):

  • Local lab test rig: Internal dispatch scaled from 0.18 ms to 178 ms under peak burst.
  • Dedicated server hardware: Internal engine processing stayed locked flat at 14 ms, even at the 2,400th operation.

(Note: Measures internal engine dispatch time. Total end-to-end latency depends on broker network geography—from where my server is currently deployed, broker RTT has ranged between 30 ms and 200 ms.)

Key Features

  • Cross-platform: MT4 ⇄ MT5 in any direction.
  • Zero local footprint: Fully managed in the cloud; no VPS, no desktop terminals running 24/7.
  • Full order lifecycle sync: Handles partial closes, SL/TP modifications, and split fills.
  • Flexible sizing: Fixed lots, equity/balance risk scaling, multipliers, and optional martingale progression modes.
  • Dynamic symbol mapping: Automated handling of broker suffixes, prefixes, and custom conventions.
  • Security: AES-encrypted credentials at rest; investor (read-only) passwords fully supported for source accounts.

Beta Testing (Demo Recommended)

The beta dashboard is live and completely free to test: https://snapcopier.com

Demo accounts are strongly recommended while testing. I’m specifically looking to expose broker-specific edge cases:

  1. Exotic symbol suffixes (.pro, .ecn, custom broker naming).
  2. Split-fills and partial closes across different broker bridges.
  3. Execution queue behavior during heavy news events.

Feedback, teardowns, and bug reports are very welcome in the comments.

u/ppolszkie — 6 days ago