DCE client consuming 30% CPU on Intel i5 6600

[DCIM_Support]

Is the DCE client  supposed to draw a constant 30% +  on a fairly modern processor ?

Seems ridiculous. Its currently sitting idle aside from whatever polling interval it needs to reach out to the server. 

I can't imagine what would require such passive processor utilization

Is this a bug? 

(CID:132669492)

[DCIM_Support]

Dear Eric Clark,

Of course not - just this is the opposite (and not the best) side of cross-platform DCE client software 😀. I.e., DCE client software is ported with minimal effort and works both on MS Windows, and on Linux or MacOS.

I think the answer to your question is better to get from the developers of Java and Eclipse, rather than from developers of DCE client software 😉. Personally, I can understand the developers of DCE-client software: they wanted to get universal cross-platform software with minimal effort.

Look in the directory C:\Program Files (x86)\StruxureWare Data Center Expert 7.5.0\dcexpert\jre and you will see Java SE (Version 8 Update 151). Then look in the directory C:\Program Files (x86)\StruxureWare Data Center Expert 7.5.0\dcexpert\features and you will see the Eclipse Platform files there, that is:

Eclipse is an integrated development environment (IDE) used in computer programming, and is the most widely used Java IDE.[6] It contains a base workspace and an extensible plug-in system for customizing the environment. Eclipse is written mostly in Java and its primary use is for developing Java applications, but it may also be used to develop applications in other programming languages via plug-ins, including Ada, ABAP, C, C++, C#, COBOL, D, Fortran, Haskell, JavaScript, Julia,[7] Lasso, Lua, NATURAL, Perl, PHP, Prolog, Python, R, Ruby (including Ruby on Railsframework), Rust, Scala, Clojure, Groovy, Scheme, and Erlang.

...and...

Eclipse uses plug-ins to provide all the functionality within and on top of the run-time system. Its run-time system is based on Equinox, an implementation of the OSGi core framework specification.

Now look in the directory C:\Program Files (x86)\StruxureWare Data Center Expert 7.5.0\dcexpert\plugins and you'll see those same DCE client software plug-ins there, for execution (read for interpretation) which requires running a separate Java VM, which I mentioned above.

That is, those 30% + CPU time, about which you wrote above - is, basically, the cost of running Java VM, and only then for execution (read for interpretation) of DCE client software plug-ins.

Conclusion: personally, I prefer and recommend using a thick client, which is a DCE client software, only for administering the DCE server, for in-depth analysis of incidents/events on graphs, tables and so on or for configuration graphical reports (i.e., Reports).

For all other tasks, i.e. for 24/7 monitoring, video surveillance, viewing of sensor charts and pre-configured in DCE client graphical reports, I highly recommend using the usual DCE-server web-GUI. Fortunately, this web-GUI exists in three implementations (for smartphones, for tablets and for PCs). I often use all three implementations and can confirm their convenience and conciseness. web-GUI is simple, reliable, and it has a good system for displaying StruxureWare Data Center Expert Events (http://DCE-address/desktop/help/events.html#events) and searching information by Using Query Syntax (https://DCE-address/desktop/help/#toc13).

If you have any further questions, please ask.

With respect.

(CID:132669674)

[DCIM_Support]

Thanks.

The CPU load seems to drop after half an hour, probably pops back up periodically, and I know that it hits 30% pretty much any time I try to run a report,  but I don't watch it all the time.

I'm not overly impressed with the Web client, so I spend most of my time in the thick client.

(CID:132669872)

[DCIM_Support]

Dear Eric Clark,

Ok, after all, I hope I could answer your question 😀.

With respect.

(CID:132670050)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.