Dear Community User! We are updating our platform to a new system.
Read more: Important information on the platform change.

cancel
Showing results for 
Search instead for 
Did you mean: 

SDK Data Layer: Result_Unknown at high load

SDK Data Layer: Result_Unknown at high load

andrhadi
Member

Hello everybody.

Currently I'm facing a problem, that the data layer returns Result_Unknown when reading an item synchronously, particularly when the CPU usage is quite high.

I'm using the CtrlX Drive integrated CtrlX Core with the framework version 02.04 w/ Ubuntu Core 22 OS. Hardware version is cx_m3_c.

Anybody faces also the same problem? And maybe somebody who knows if it is a common "normal" performance problem? Any feedback is highly appreciated.

Many thanks in advance.

 

4 REPLIES 4

CodeShepherd
Community Moderator
Community Moderator

Could you specify what "CPU usage is quite high" means? Which CPU has which utilisation level?

andrhadi_0-1711011177737.png

I noticed that the system responsiveness is quite bad (handling in the WebGUI) - eventhough the CPU load is only about 15-20% (that's why I wrote CPU usage was quite high). I have the impression that the above CPU load chart is not telling us the whole truth - to bear analogy with the Task Manager in Win10 which always is telling us low load but system responsiveness is terrible.

Especially the high cache memory allocation is remarkable.

A view into the process monitor shows a quite high memory allocation credit to Device Admin.

andrhadi_1-1711011495022.png

My apps are the Data Provider by DC-AE/SVC2 and Service Indicator Control Web Appl.

Is this behaviour normal?

Unresponsiveness is not normal but the Storage allocation for caching purposes is fine and will be reduced dynamically if necessary. "Device Admin" is one of central processes in the system.

What about the Windows load on your PC? Unresponsiveness often is also related to PC or network issues/load. Can confirm behavior with another PC?

Could you share a screenshot and/or the whole data of the response of the data layer?

Are there any news? Is this issue still open?

Icon--AD-black-48x48Icon--address-consumer-data-black-48x48Icon--appointment-black-48x48Icon--back-left-black-48x48Icon--calendar-black-48x48Icon--center-alignedIcon--Checkbox-checkIcon--clock-black-48x48Icon--close-black-48x48Icon--compare-black-48x48Icon--confirmation-black-48x48Icon--dealer-details-black-48x48Icon--delete-black-48x48Icon--delivery-black-48x48Icon--down-black-48x48Icon--download-black-48x48Ic-OverlayAlertIcon--externallink-black-48x48Icon-Filledforward-right_adjustedIcon--grid-view-black-48x48IC_gd_Check-Circle170821_Icons_Community170823_Bosch_Icons170823_Bosch_Icons170821_Icons_CommunityIC-logout170821_Icons_Community170825_Bosch_Icons170821_Icons_CommunityIC-shopping-cart2170821_Icons_CommunityIC-upIC_UserIcon--imageIcon--info-i-black-48x48Icon--left-alignedIcon--Less-minimize-black-48x48Icon-FilledIcon--List-Check-grennIcon--List-Check-blackIcon--List-Cross-blackIcon--list-view-mobile-black-48x48Icon--list-view-black-48x48Icon--More-Maximize-black-48x48Icon--my-product-black-48x48Icon--newsletter-black-48x48Icon--payment-black-48x48Icon--print-black-48x48Icon--promotion-black-48x48Icon--registration-black-48x48Icon--Reset-black-48x48Icon--right-alignedshare-circle1Icon--share-black-48x48Icon--shopping-bag-black-48x48Icon-shopping-cartIcon--start-play-black-48x48Icon--store-locator-black-48x48Ic-OverlayAlertIcon--summary-black-48x48tumblrIcon-FilledvineIc-OverlayAlertwhishlist