The Doctor Binding helps find issues with your system [4.0.0;4.9.9]

[matt1 (Skinah)]

I have compiled the binding into a V5 jar found here in the marketplace:

The Doctor Binding helps find issues with your system [5.0.0;5.9.9]

This binding is one I have been thinking of building for a while, it is designed to help diagnose issues on someones system that does not know Linux/Java and has no idea what free VS available ram means, let alone the Java heap. Install the binding and get a system check up. The system info binding requires you to know what to look at and how to interrupt the results, this binding will hopefully over time get better at finding issues in an automated way. If you have some ideas on what it can che…

I am planning on adding some new functionality to the binding soon so I have been testing the V5 for the past 3 weeks and it is working fine on my system.

@Larsen

I was on 64 bit already with OH4. But as I got no performance problems at all I don’t see anything to worry about

Yes I also saw my heap jump in size when moving to V5….

You have changed some or all of the following :

1. a 64bit OS

2. 64bit java or a different java version number.
3. openhab compiled for the newer java, will be optimized for 64bit.

I believe I was using a 64bit OS and JAVA already, but now all of openHAB is compiled for the newer java. It may also be how this binding ‘cleans’ the heap before taking a reading of the used heap. When you ask the heap to be cleaned, it can be a recommendation to clean the heap, and there are two types of garbage collection that can be run. Each java VM may implement the garbage collection in its own way, so changing to a different java version or brand of JVM can result in a different result.

I am no expert but as you said its nothing to worry about unless your heap is now close to being full.