Forum Discussion

anttijarvinen's avatar
anttijarvinen
Frequent Visitor
2 years ago
Solved

On-premises gateway throttling issue

Hi,   I encountered a problem while testing load balancing with two on-premises gateways, with the other instance throttled.   Following these instructions https://learn.microsoft.com/en-us/data-...
Need Help
  • lbendlin's avatar
    lbendlin
    2 years ago

    Why are you torturing the VM? Gateway cluster members should have at least 16GB, but better 32GB. 8GB will always lead to memory starvation.

anttijarvinen's avatar
anttijarvinen
Frequent Visitor
2 years ago

Very interesting in deed, would love to see what your monitoring actually consists of.

 

I interpret what you say about performance so, that it's hard to set any definite rules, and it's more based on the the actual workloads. We have many datasets or dataflows of varying sizes and of varying amount of data sources, but very few direct queries. So I guess the mashup performance is the most important aspect (maybe also spooling?)..

Memory has never been a problem based on instance monitoring (after we optimized some too complex queries).

 

Can you clarify what you mean about "configured exactly the same". Isn't the gateway-software abstracting away the actual machine running it? - Isn't it enough that the gateway sw-versions match, and their settings are ok?

lbendlin's avatar
lbendlin
Icon for Super User rankSuper User
2 years ago

The cluster members must have the exact same driver versions for your connections, the TNS entries must match, the ODBC system DSNs must match, the gateway config files must match (all of them), they must all be on the same Windows patch level and and and.   The moment you have the slightest difference something will break  in a random fashion and you will waste a lot of time chasing it down.