Looking for suggestions on server set up E10.1
35 users (80/20 split full, MES)
All services will be on one server. Coming from 6.1 and re-implementing only bringing what we need to.
Current DB size 4.2 GB
Current scenario
Light to moderate reporting with crystal now.
MRP at Night
PO Suggestions daily
Fairly Vanilla setup
Epicor hardware sizing guide recommendation for a medium ERP
Dell R730
1 x Xeon® E5-2667 v4 3.2GHz,25M Cache,9.60GT/s QPI,Turbo,HT,8C/16T
64 GB (4 x 16GB RDIMM, 2400MT)
Perc H730P 2GB cache
2 x 300 GB SAS 10K OS Raid 1
4 x 200 GB SSD MLC SQL Raid 10
Intel 1350 QP Nic
I was looking at configuring the server along these lines
1 x Xeon® E5-2667 v4 3.2GHz,25M Cache,9.60GT/s QPI,Turbo,HT,8C/16T
64 GB (4 x 16GB RDIMM, 2400MT)
Perc H730P 2GB cache
2 x 300 GB SAS 10K OS Raid 1
4 x 200 GB SSD MLC SQL DB Raid 10
2 x 200 GB SSD MLC Tran Logs Raid 1
2 x 200 GB SSD MLC Temp Db Raid 1
2 x 200 GB SSD MLC Reports Raid 1
Intel 1350 QP Nic
In the next year I could see us adding 3-5 users. For performance consideration would it be better to add another processor, more drives, memory or build a second reporting server down the road.
I found the Epicor hardware sizing guide was underspec’d for our environment.
We are running a few more users than you and running multi-company.
We have separated our application server and database server, I recommend this for performance. Also recommend SSD for all drives these days unless you need the space.
I am seeing some CPU spikes with and overall high CPU usage. Just ordered a new application server to upgrade to a dual socket CPU 8 cores each.
Are you planning to run the application server and database server on the same system?
Are you visualizing the servers?
We’re only at 15 users, and our IT dept (actually the corporate IT) decided to go with separate boxes for the SQL server and the AppServer.
They do everything as a Virtual Server (something like VMWare, but not VMWare). They have an entire data center for world-wide operations - something like 500 servers (virtualized). So I can’t help you on the hardware specs. But I was assured that adding resources (memory, disk space, CPU’s etc…) was a snap, and was only limited by the O/S.
We’re using WinServer 2012R2 for the AppServer and whatever the required matching SQL Server version is. The setup guide was pretty adamant about having specific pairs of O/S’s when going with separate App and DB servers.
We are at about 50 consecutive users and are happy with a single box 2x E5-2667s, 128GB and 2x256 4x500 SSDs raid 10 on 2012R2. Epicor flies on my laptop but there are some issues with the older i5s we run.
We have 5 companies in 3 continents running off of ours.
We’re also upgrading to 10.1 soon, anyone have experience on running Epicor in virtual environment?
Planning on hyper-v with 2x E5-2667v4, 96GB ram and some ssd in RAID1 and server 2016 (of course VM are in 2012R2)
15 simultaneous users, I’m so careless forgetting this, E9 db in progress is 7GB
should appserver and SQL in separated VM or one VM is enough for 15 users?
may be getting more ram to 128GB as there are other VMs
For 15 Simultaneous what you have indicated for specs CPU and RAM wise should be plenty enough. I find that Epicor bottlenecks a lot of times at the Drives so make sure your drive configuration is optimal. What speed is the backplane and are you going to use SAS or just straight SATA SSD?
just SATA SSD, probably a few intel s3610
It’d be a Dell R730 with Perc H730P 2GB cache raid card, but I can’t find much about backplane on Dell site
hardware sizing guide suggests each appserver VM to be 4 CPU and 12GB ram, and each SQL VM 4 CPU 24GB ram, but didn’t talk much about scaling nor even a 1 VM solution
If you are going to use consumer SSD I would highly recommend the Samsung Pro 850 drives. Though the Intel would be right up there with them.
Your H730 will have a 6gbps SATA and 12gbps SAS.
I have found through research that there is a mild debate between using RAID10 with SSDs or to not. I would use RAID10 for your drive that the Epicor Database will sit on, and use RAID1 for the Host OS, and guest OS.
You will need at a minimum (if you were to run nothing else on this box) 3 arrays and 8 disks for a somewhat optimal setup.
We have 70 users running on a 103~ GB database per instance. There are lots of reports external software integration and EDI running nearly all the time and the client performance is part limited by the Client PCs, but in general good. Putting your erp on two boxes just means your going to have a chatty ERP system talk over the network alot. We have both the Live, Test system , Enterprise Search, Epicor Web Access, and SSRS all on the same box. All perform well (well Enterprise search isn’t good enough to index all our data but that is another story)
Box Setup
Windows Server 2012 R2
Physical Setup
Hardware
Dell R630
2 x Intel Xeon E5-2667 v3
256 GB RAM (219~ in use. SQL has topped out at 193 GB)
Dell iDrac (just because its cool)
Dell H710 PERC RAID card
Drives (All in RAID 1)
2x Consumer SSDs for os
2x Consumer SSD for Epicor IIS
1 x Samsung Enterprise PCIE SSD for live DB + LOG
2 x Consumer HD for Test, SSRS Db, Crystal Reports
2 x 7k Mechanical for Temp Storage of the SQL Backup
Personal advice at a high level - we have some excellent Perf folks so I will never argue with their specifics and of course they are forced as we all are into the caveat that everyone’s data loads and usage is different so measure!
ERP10 is a db intensive system. Not as bad as E9 but still does a LOT of SQL IO. Plan accordingly with your disk subsystem. Also, take the load off if possible. Standard SQL DBA tricks on log vs data, etc all apply. Also if needed, offload reporting to a replicated db to push the IO load onto it for reports. This is vanilla SQL Replication. The E10 schema was designed to play nice with SQL Replication so don’t be afraid of E10 replication being worse than any other replication.
Second, the Tasks - Processes and Reports - can use substantial amounts of memory since we give you the power to ‘download the internet’ with free form BAQs, etc. This is very flexible for you (Imagine asking Epicor for every custom report - ick all around). With that power however you can eat up a bunch of memory in the app server. Throwing extra RAM at the app pool is a good thing. A variation on this is placing Tasks on a second app server. That way if someone is crunching a huge report, posting engine, mrp, etc it does not destroy end user usage and experience.
dotNet enjoys multiple cores so having an extra in the app tier is always a good thing.
No mention of fail over. When I see all in one I always ask if you are ready for being down for some time in your business. How long will it take you to stand things back up? Is that acceptable?
