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
  • LPC is local, so that'll be pretty instantaneous. Any remote connection will be incomparable, honestly.

    You're using RPC over HTTPS to what machine? Your Azure test instance? Is this in the M-Files cloud or in your own infrastructure?

    There's obviously an overhead of using RPC over HTTPS but that impact seems far (far!) too much to be blamed on just the protocol.

    Regards,

    Craig.
Reply
  • LPC is local, so that'll be pretty instantaneous. Any remote connection will be incomparable, honestly.

    You're using RPC over HTTPS to what machine? Your Azure test instance? Is this in the M-Files cloud or in your own infrastructure?

    There's obviously an overhead of using RPC over HTTPS but that impact seems far (far!) too much to be blamed on just the protocol.

    Regards,

    Craig.
Children
No Data
M-Files
M-Files Support


© 2025 M-Files, All Rights Reserved.