I'm interested in the inner working of the trend data loading from a DB cluster.
Let's assume there are two sites, a main site and a remote site, where the DB cluster is located in the main site.
When trending is requested for an element running on the remote site, will DataMiner request the data to the remote DMA even if the data is in a DB cluster on the main site?
Or is the database request done from the DMA you connect to with the Cube client?
Depending on the method I think there is a speed difference in the loading of the trending.
Someone connected on a DMA on the main site will have a much faster loading speed if the DB request goes directly instead of through a DMA in the remote site.
If the request goes through the remote site, are there any possibilities to address this in the software?
Hi Miguel, no it’s DMA’s in a different site but in the same DMS
Jeroen,
The answer is the request first goes to the remote site, then the request goes to the clustered database. So you get indeed multiple network hops. There are indeed still improvements that can be made in the scenario of a clustered database.
Hi Jeroen,
With a remote site, are you referring to a DataMiner Probe? Could it be the case that the main site contain a replicated element representing the element in the remote site?