We are also using a server on the same network as the E9 server for running the Epicor client via a RemoteApp.
This works ok and the compression setting wouldn’t come into play.
What I’m referring to is trying to pull data from the OpenEdge database via ODBC.
The time it takes to pull big tables, like PartTran, is painful.
JOE ROJAS
Epicor Applications Manager
VENTION MEDICAL
DIRECT: 508.597.1392 x1625 | MOBILE: 774.826.9245
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Thursday, June 09, 2016 10:32 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Re: E9: Install E9.05 on Windows 10
Joe,
Virtual Box or Hyper-V on windows 10 will work. Virtual Box is pretty slick now these days.
I'd be really curious if anyone has attempted to make a Docker container for E9 or E10 though.
With regards to hosting and performance, are the user accounts setup to use compression, and have you tried playing with the compression settings in the default.mfgsys?
You can use the configeditor.exe from the client directory if you are not keen on editing the file directly.
Since installing E9 we have seen our fair share of performance issue, What I can say is that increased network bandwidth and client RAM appears to have a big impact. On the server side using Nvme disks (Intel P3700) for the EpicorData folder and the SQL database and log files made an improvement.
What sort of bandwidth do you have between your App server and your client workstations?
Kind Regards
Simon Hall
[Non-text portions of this message have been removed]