Sumit Potbhare

Microsoft Dynamics AX for Retail

Archive for the tag “POS performance”

AX 2012 R3 Benchmark | Retail and Distribution

Hi Guys, I have been working on POS performance from last couple of days and found few interesting information that I would like to share with you.

Microsoft conducted a 24-hour “day in the life” benchmark of Microsoft Dynamics AX 2012 R3 to measure the application’s performance and scalability characteristics when running retail and distribution workloads. The benchmark ran a variety of functional scenarios that use different client and integration technologies, thereby providing a broad view of enterprise resource planning (ERP) workload performance on AX 2012 R3.

Benchmark.png

Read more…

ePOS Performance | Switch speed from Online to Offline mode

Hi Guys, This is the second blog from my ePOS performance blog series. You might have viewed my last blog on ePOS | Retail Implementation using SQL Express which will help you in reducing the Database size when dealing with SQL Express. Here we will talk about reducing the time for ePOS to switch between Online to Offline mode. Read more…

ePOS Performance | Offline sync service utilizing 100% CPU usage

Hi Guys, You might have viewed my last blog on ePOS | Retail Implementation using SQL Express which will help you in reducing the Database size when dealing with SQL Express. In this blog I would like to explain further on the performance issues that occurs even after reducing the Database size. One of them is “Offline sync service utilizing 100% CPU usage”.

As I earlier said, Retail implementation becomes challenging, when you enable offline mode.

 

highcpuusage

Read more…

ePOS | Retail Implementation using SQL Express

Hi Guys, in this blog I want to share my experience regarding use of SQL express for ePOS (Enterprise POS) – Online Database and Offline Database. The experience is from my recent Dynamics AX Retail project having 300 stores with nearly 620 terminals all using SQL express for Online and Offline Database.

Few of the issues which we faced were –

  • DB size growing
  • 100% CPU usage
  • Slowness in Retail operations

SQLExpress.png

Read more…

Post Navigation