SAP Customer Checkout Improving performance with high volume of articles, Advice needed.

[former_member765884]

Customer checkout ( SAP CCO 2.0 SP12 PL00) is deployed on a PC, Specs are

Operating System:

Microsoft Corporation, Windows 10 Enterprise Evaluation (10.0.19042) (en-GB)

Processor(s):

Intel(R) Celeron(R) CPU J1900 @ 1.99GHz (4 virtual) (X64)

Available Memory:

203 MB / 3969 MB

Articles imported from customer checkout manager is now ~1.2 million. Using the “Search” functionality can be slow, depending upon whether we use “Basic Search” or “Advanced Search”; and it is also very dependent upon what search terms and table columns are searched. Can the search be configured to specific columns which are relevant to us? Is there a way to retrieve the articles from hard disk instead of holding in memory? ( I understand that CCO is browser based).

No receipt data or inventory on the till at the moment and I'm assuming that the performance issues will increase when transactions are added as well. I have configured the run.properties file as well.

So the main question is, is this performance expected given the PC specs? We have tested on machines with 8GB and have had better performance but again this is with no transactions, just articles.

Any observations or advice would be greatly appreciated.

[anderson_schmitt]

Hi ghazzali,

If you are still facing the performance issue, I suggest you to open an incident with the SAP Support.

Regards,
Anderson

[anderson_schmitt]

Hello Ghazzali,

What are the values of the run.properties file?
Is the file "run.properties" saved at C:\SapCustomerCheckout\ path?
Is the Java 32bits or 64bits?

Also review the KBA 2839737 for further information, please.

Regards,
Anderson

[former_member765884]

Hi Anderson,

Thank you for the reply.

The values of the "run.properties" files is "InitialMemory = 384m", "MaxMemory = 2304m" and "MaxMetaspaceSize = 768m".

The "run.properties" is saved at C:\SapCustomerCheckout\. This is three times the initial memory allocation.

Also, Java is 64 bit. OpenJDK 64-Bit Server VM SapMachine.

I reviewed KBA 2839737 and

2. Synchronization jobs are scheduled at tight intervals ( scheduled for daily at 3 am).

3. Enable central monitoring and / or Enable central monitoring system logging is activated ( Disabled this.)

Ran restarted POS and timed the article search, 2 minutes and 20 seconds to display the results.

So still experiencing the slow return when searching for articles.