Options
  • Locked Locked
  • Replies 6 replies
  • Subscribers 9 subscribers
  • Views 511 views
  • Users 0 members are here
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

RPC over Proxy setup

dejan
Hi M-Files team and community,

We are using RPC over Proxy setup as described here: www.m-files.com/.../rpc_over_http.html.
We were able to enable access over proxy and over https.

Even though I have a quite solid internet speed (49 MBps Download, 12 Mbps Upload), when I try connection over M-Files client I get only 1,68 MBPs Download and 1,39 MBps Upload. Is such degradation expected when connection is setup over proxy?

We have test environment in Azure. Of course, this for sure cause latency. What would be realistic degradation in network throughput when using RPC over HTTPs instead of LPC protocol?

Thanks.

Dejan
Parents
  • Thank you for answers.

    @CraigHawker: Our own Azure instance.

    @bright-ideas.dk: even though I have used my local client for quite some time (so all modules should be awake), I am still not reaching anything close to my network throughput. My continuous tests in short intervals make maximal throughput of 4 MBps.

    Our plan is also to host it on premise in future so hope that we will be able to utilize that throughput.

    So, it must be latency to Azure or we missed something in our configuration but than I would assume it would not work at all!?
    We have basically Proxy and MFiles on same virtual server in Azure. We are using 443 port for web page and 4466 for desktop client.

    Thanks
Reply
  • Thank you for answers.

    @CraigHawker: Our own Azure instance.

    @bright-ideas.dk: even though I have used my local client for quite some time (so all modules should be awake), I am still not reaching anything close to my network throughput. My continuous tests in short intervals make maximal throughput of 4 MBps.

    Our plan is also to host it on premise in future so hope that we will be able to utilize that throughput.

    So, it must be latency to Azure or we missed something in our configuration but than I would assume it would not work at all!?
    We have basically Proxy and MFiles on same virtual server in Azure. We are using 443 port for web page and 4466 for desktop client.

    Thanks
Children
No Data
M-Files
M-Files Support


© 2025 M-Files, All Rights Reserved.