Skip to main content

Hi IFS Community!

IFS Version is Cloud 24R1 SU9

We have an SFTP Reader in IFS Connect that is struggling to process files that are >100KB. We’ve been able to process files without issue smaller than that, having the files listed in Connect Reader Queue and then passed along to Application Messages where they will fail to pass the IFS business logic (which is to be expected). IFS support has suggested increasing the memory to the middletier server, increasing it from 40GB of RAM to 48GB of RAM.

One thing that I’m curious about tuning wise is how to assign more memory specifically to the ifsapp-connect pod. Performing a describe on the current pod has a section that I’m thinking I would like to have increased, but am not certain how best to implement.

    Limits:
      cpu:                10
      ephemeral-storage:  2G
      memory:             3G ← this one here

This is certainly some “low level” tuning, but am curious if anyone here has successfully implemented a specific tuning of memory resources for the ifsapp-connect pods.

Thank you,

Randy

 

Hello there ! 

Very interested on this topic. 

​@EsiRandyG  did you find a way to get it sorted out ? I’m wondering myself how these pods memory values can be set in some configuration files to make the pods more efficient. 

It wouldn’t be on the limits but more in some “request” tag that this could be set, right ? 
If so, where do you set it ? 

Hi ​@pabdou - I ended up submitting a case with IFS support to help resolve this. I was ultimately instructed to not try attempting to modify the individual pods, but to increase the memory allocated to the middletier server initially. This was ultimately not implemented, as updating the Logging Properties for the framework.level and integration.level from WARNING to DEBUG seemed to correct part of the issue, and I’m now able to process significantly larger files. Path to the form is JSF Properties > Logging Properties. I’m not exactly convinced this helped with anything and may have just been a coincidence.

Sorry if this isn’t terribly helpful, but maybe adjusting the logging level will allow you to collect the logs using kubectl to get any additional insight on the performance issue you may be encountering.

 

Have you tried experimenting with Kubernetes as you mentioned in your post changing the individual pod specifications? Did it help resolve the issue?

Hello there ! 

Very interested on this topic. 

​@EsiRandyG  did you find a way to get it sorted out ? I’m wondering myself how these pods memory values can be set in some configuration files to make the pods more efficient. 

It wouldn’t be on the limits but more in some “request” tag that this could be set, right ? 
If so, where do you set it ? 

Manual Memory Allocation for Pods in ifscloud-values.yaml

You can manually allocate memory to specific pods using the addMemory directive in the ifscloud-values.yaml file. For example:

 

⚠️ Note

We encountered issues with pods being OOMKilled (Out of Memory). The default memory settings were insufficient, even on servers with 128 GB of RAM.

After analyzing memory usage via Grafana, we observed that only about 10% of the available memory was being utilized. To mitigate this, we manually added the addMemory directive to increase the memory allocation for the affected pods.

#This is a collection of small applications like - apidoc - demand server proxy - gisint - svcsch
ifsappapplicationsvc:
  #replicas: 0
  addMemory: 4000

 

 

 

Hello, thank you for the answer ! 

For the addMemory setup set to 4000, what does the 4000 means  ? 

How can i know which value I should put ? :) 

Thank you for your help 

 

Hello there ! 

Very interested on this topic. 

​@EsiRandyG  did you find a way to get it sorted out ? I’m wondering myself how these pods memory values can be set in some configuration files to make the pods more efficient. 

It wouldn’t be on the limits but more in some “request” tag that this could be set, right ? 
If so, where do you set it ? 

Manual Memory Allocation for Pods in ifscloud-values.yaml

You can manually allocate memory to specific pods using the addMemory directive in the ifscloud-values.yaml file. For example:

 

⚠️ Note

We encountered issues with pods being OOMKilled (Out of Memory). The default memory settings were insufficient, even on servers with 128 GB of RAM.

After analyzing memory usage via Grafana, we observed that only about 10% of the available memory was being utilized. To mitigate this, we manually added the addMemory directive to increase the memory allocation for the affected pods.

#This is a collection of small applications like - apidoc - demand server proxy - gisint - svcsch
ifsappapplicationsvc:
  #replicas: 0
  addMemory: 4000

 

 

 

 

Hello, thank you for the answer ! 

For the addMemory setup set to 4000, what does the 4000 means  ? 

How can i know which value I should put ? :) 

Thank you for your help 

 

Hello there ! 

Very interested on this topic. 

​@EsiRandyG  did you find a way to get it sorted out ? I’m wondering myself how these pods memory values can be set in some configuration files to make the pods more efficient. 

It wouldn’t be on the limits but more in some “request” tag that this could be set, right ? 
If so, where do you set it ? 

Manual Memory Allocation for Pods in ifscloud-values.yaml

You can manually allocate memory to specific pods using the addMemory directive in the ifscloud-values.yaml file. For example:

 

⚠️ Note

We encountered issues with pods being OOMKilled (Out of Memory). The default memory settings were insufficient, even on servers with 128 GB of RAM.

After analyzing memory usage via Grafana, we observed that only about 10% of the available memory was being utilized. To mitigate this, we manually added the addMemory directive to increase the memory allocation for the affected pods.

#This is a collection of small applications like - apidoc - demand server proxy - gisint - svcsch
ifsappapplicationsvc:
  #replicas: 0
  addMemory: 4000

 

 

 

 

Hello, thank you for the answer ! 

For the addMemory setup set to 4000, what does the 4000 means  ? 

How can i know which value I should put ? :) 

Thank you for your help 

 

Hello there ! 

Very interested on this topic. 

​@EsiRandyG  did you find a way to get it sorted out ? I’m wondering myself how these pods memory values can be set in some configuration files to make the pods more efficient. 

It wouldn’t be on the limits but more in some “request” tag that this could be set, right ? 
If so, where do you set it ? 

Manual Memory Allocation for Pods in ifscloud-values.yaml

You can manually allocate memory to specific pods using the addMemory directive in the ifscloud-values.yaml file. For example:

 

⚠️ Note

We encountered issues with pods being OOMKilled (Out of Memory). The default memory settings were insufficient, even on servers with 128 GB of RAM.

After analyzing memory usage via Grafana, we observed that only about 10% of the available memory was being utilized. To mitigate this, we manually added the addMemory directive to increase the memory allocation for the affected pods.

#This is a collection of small applications like - apidoc - demand server proxy - gisint - svcsch
ifsappapplicationsvc:
  #replicas: 0
  addMemory: 4000

 

 

 

 

4000 means 4 GB ;)

Ok, straitght forward :D 

 

Thank you very much, I’ll try that at some point 

Terms & ConditionsCookie settings