The problem has less to do with CIFS, and more to do with applications
and the laws of physics.
The laws of physics dictate that large files opened from far away will
not perform like those that are close, and applications must be designed
to deal with those realities. This is one reason why terminal services
and remote desktop get a lot of traction in business. It allows data to
sit near the application, and send just the UI data to the remote party
(Remote Desktop as an application is mature, and works well).
There is no panacea. There are only varying levels of compromise to
make usable work flows. Even the examples I've seen of traditional LAN
applications which have been completely rebuilt to become Cloud apps are
thought to be less 'performant' by users, ergo, also a compromise.
What will work best all depends on the business process you're trying to
create. Good luck.
-K
On 7/25/2016 2:22 PM, Chris wrote:
Karl Fife wrote:
Are you sure that CIFS is slow because of PPTP? All but the latest
CIFS/SMB protocols are poorly suited for high-latency connections such
as the public Internet (e.g. where you might use VPN). Even under the
best circumstances, many applications don't tolerate it well
(Size/speed/latency/loss etc.)
BTW: Is there any alternative to CIFS? Any parameters to speed it up? Is
there any replacement? I would use SFTP, but its usability is sth.
completely different for non-powerusers.
- Chris
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
