Interesting question! DataMiner indeed runs a mix of 32 and 64 bit processes. In short, the processes potentially requiring lots of memory on bigger systems (more than 4GB) are running 64 bit, the other processes might still run 32 bit, it will be a mix.

(1) This doesn't really impact the performance of a DataMiner System, it more has impact on how much memory a process can handle and therefore how much one DataMiner Agent can handle. Therefore, the processes potentially going beyond the 4 GB mark (= max memory a 32 bit address can handle), are all running 64 bit. In one of the upcoming versions of DataMiner, SLProtocol will also by default run 64 bit, it used to be 32 bit, but you have 5 of these SLProtocol processes, so in some rare cases you might need to opt for the 64 bit version which we will now make the default for all systems.

(2) There are still a number of 32 bit processes in DataMiner, those are C++ processes which require some work and validation to switch them to 64 bit, so we typically only do this when it is needed. Certain processes, like e.g. SLLog, will never need that much memory, so we won't immediately change such processes, as there is no need and no advantage in doing so.

(3) In terms of roadmap, and I believe all processes potentially requiring more than 4GB memory, are already running 64 bit. SLProtocol was the last one, where you still had a choice, and now we'll bring this one to 64 bit by default as well. Then I don't think there are other processes on our radar to switch them, but feel free to bring them to our attention if there would be any.

Note that newer processes like DataMiner Extension Modules (DxM) are all running managed code and this runs anyCPU anyhow, so those are all running 64 bit. Only the C++ processes might still run 32 bit, and only the ones which are not supposed to go beyond the 4 GB mark.

Let me know if something would not be clear.

Bert