Epicor Server Performance: Cores vs Clock Speed

Yahoo Archive
1
E9 Progress 32 Bits... SIGH ok so the issue there is slightly different

Your App Server (Progress) Runs a Number of Worker Threads (you can see how my in your Open Edge Explorer)
That number can be defaulted to X and it does NOT multi thread past that point.
Once X number of Worker Threads are busy it just waits till one becomes free (which is why sometimes your server will halt or get stupid)
So I guess in this case Faster Cores and maxing out the worker threads to match the number of cores would benefit you (slightly) since each thread would perform "faster" however again that is theoretical. What difference in clock speed are we talking about? 2.3 to 2.5? or is there a SIGNIFICANT difference?
If the difference in clock speed is small ... then I would still go with more cores.




Jose C Gomez
Software Engineer


T: 904.469.1524 mobile

Quis custodiet ipsos custodes?

On Thu, Jul 16, 2015 at 12:18 PM, jason.navarrete@... [vantage] <vantage@yahoogroups.com> wrote:

 
<div>
  
  
  <p></p><div>Thanks Jose.</div><div><br></div>Right now we&#39;re on E9 (9.05.702A, Progress 32-bit on Windows 2008 R2). If we get new hardware it&#39;d be nice if it was also capable of running E10.<p></p>

</div><span class="ygrps-yiv-1380662103">
 


<div style="color:#fff;min-height:0;"></div>


2

If you had to choose, would you pick more cores at a lower clock speed or fewer cores at a higher clock speed? Why?


With our current server we ended up with a 2 x 8 setup instead of 2 x 12 since I was going for higher speeds at the time, but I'm curious what y'all have seen...


I'm still amazed that at 41 users on SQL the recommendation starts towards three servers under medium load.


Thanks and happy Friday!

3
Bump. Anyone?
4
Ok So What Version of Epicor? 10?

E10 runs on a Single IIS App Pool and a Single w3wp process (unless configured otherwise)
That means that any incoming Request hits a Single IIS Process and assuming that Epicor wrote their app properly and your IIS is configured right it should process each WCF call in its own thread from the given ThreadPool.
Now I am making a thousand assumptions here... but lets hope everything was implemented optimally (hahah)

Then Clock Speed shouldn't really matter... I mean Epicor is not a CPU bound application and there are very few if any calls that would benefit from the higher clock speed... You are talking about nano seconds.... (or even less). The Issue with Epicor is generally IO Problems on the SQL Side.

So I would say higher core count would be more beneficial (theoretically)



Â


Jose C Gomez
Software Engineer


T: 904.469.1524 mobile

Quis custodiet ipsos custodes?

On Thu, Jul 16, 2015 at 11:26 AM, jason.navarrete@... [vantage] <vantage@yahoogroups.com> wrote:

 
<div>
  
  
  <p>Bump. Anyone?</p>

</div><span class="ygrps-yiv-29772963">
 


<div style="color:#fff;min-height:0;"></div>


5
Thanks Jose.

Right now we're on E9 (9.05.702A, Progress 32-bit on Windows 2008 R2). If we get new hardware it'd be nice if it was also capable of running E10.