Slow upload\download speed

[edakacj]

Hello!

I have launched two proxy servers on my server:

1. https://hub.docker.com/r/whn0thacked/telemt-docker
   running on port 443

2. https://github.com/SamNet-dev/MTProxyMax
   running on port 8443

In the case of MTProxyMax, I am experiencing low download speeds in Telegram.

I ran some tests:

1. [443] 30 MB downloaded in 5 seconds
2. [8443] 30 MB downloaded in 60 seconds

The difference is significant.

I really like the functionality for creating user accounts and setting quotas.
However, the low speed prevents me from switching to your solution.

Is there anything that can be done about this?

[SamNet-dev]

Hey, thanks for reporting this with the benchmarks — really helped pinpoint the issue.

Both MTProxyMax and the other image you tested use the same telemt engine underneath. The speed difference was caused by MTProxyMax running the container with Docker CPU and memory limits (--cpus 1, --memory 256m), which artificially throttled throughput even if your server had plenty of resources.

Here's what I changed:

1. Removed the default resource caps — the container now runs with no CPU/memory limits by default, using your full system resources. You can still set custom limits during setup or in settings if needed.

2. Added LTO build optimizations — the engine is now compiled with link-time optimization for a faster binary. A new Action build is running now and should be live soon.

To get the fix:

mtproxymax update

This will pull the latest version and restart your proxy without the caps.

One more thing — you're running the other proxy on port 443 and MTProxyMax on 8443. Some ISPs treat port 443 (standard HTTPS) as priority traffic and may throttle non-standard ports. To get a fair comparison, after updating try switching MTProxyMax to port 443 as well (you can change it in settings). That way you'll be comparing both proxies under the same conditions.

Let me know how it goes!

[goodboy34-tech]

И MTProxyMax, и другое протестированное вами изображение используют один и тот же движок telemt, расположенный под ним. Разница в скорости была вызвана тем, что MTProxyMax запустил контейнер с ограничениями процессора Docker и памяти (--cpus 1, --memory 256m), что искусственно ограничивало пропускную способность, даже если на вашем сервере было много ресурсов.

Не лучшей ли практикой будет ограничить контейнер в % соотношении, а не в жестком? Все мтпрокси, которые я когда-либо запускал, имеют проблемы с утечкой.