Memory spikes on AWS EC2

[satviktechie1986]

I am using ocelot Version="24.0.0" in .net 7 microservices to route request from front end applications , but sometime i am running into sudden memory spikes on aws ec2 , initially memory was near 8% that went to 16% somehow on ec2 and it not getting down during off business working hours , below is my ocelot configuration in program.cs

builder.Configuration.AddJsonFile($"Ocelot/ocelot.{builder.Environment.EnvironmentName}.json", optional: false, reloadOnChange: true);
builder.Services.AddOcelot(builder.Configuration);

await app.UseOcelot();

"ocelot.production.json" file:

{
  "Routes": [
    {
      //Insurance API
      "DownstreamPathTemplate": "/api/{everything}",
      "DownstreamScheme": "http",
      "DownstreamHostAndPorts": [
        {
          "Host": "xxx",
          "Port": 80
        }
      ],
      "UpstreamPathTemplate": "/api/insurance/{everything}",
      "UpstreamHttpMethod": [ "POST", "PUT", "GET", "DELETE" ]
    },
    {
      //CRM API
      "DownstreamPathTemplate": "/api/{everything}",
      "DownstreamScheme": "http",
      "DownstreamHostAndPorts": [
        {
                    "Host": "xxx",
          "Port": 80
        }
      ],
      "UpstreamPathTemplate": "/api/CRM/{everything}",
      "UpstreamHttpMethod": [ "POST", "PUT", "GET", "DELETE" ]
    },
    //Operation API
    {
      "DownstreamPathTemplate": "/api/{everything}",
      "DownstreamScheme": "http",
      "DownstreamHostAndPorts": [
        {
                    "Host": "xxx",
          "Port": 80
        }
      ],
      "UpstreamPathTemplate": "/api/operation/{everything}",
      "UpstreamHttpMethod": [ "POST", "PUT", "GET", "DELETE" ]
    },
    //Sales API
    {
      "DownstreamPathTemplate": "/api/{everything}",
      "DownstreamScheme": "http",
      "DownstreamHostAndPorts": [
        {
                    "Host": "xxx",
          "Port": 80
        }
      ],
      "UpstreamPathTemplate": "/api/sales/{everything}",
      "UpstreamHttpMethod": [ "POST", "PUT", "GET", "DELETE" ]
    },
    //Address API
    {
      "DownstreamPathTemplate": "/API/{everything}",
      "DownstreamScheme": "http",
      "DownstreamHostAndPorts": [
        {
                    "Host": "xxx",
          "Port": 80
        }
      ],
      "UpstreamPathTemplate": "/api/address/{everything}",
      "UpstreamHttpMethod": [ "POST", "PUT", "GET", "DELETE" ]
    },

    //Property API
    {
      "DownstreamPathTemplate": "/API/{everything}",
      "DownstreamScheme": "http",
      "DownstreamHostAndPorts": [
        {
                    "Host": "xxx",
          "Port": 80
        }
      ],
      "UpstreamPathTemplate": "/api/Property/{everything}",
      "UpstreamHttpMethod": [ "POST", "PUT", "GET", "DELETE" ]
    },

    // Document API
    {
      "DownstreamPathTemplate": "/api/{everything}",
      "DownstreamScheme": "http",
      "DownstreamHostAndPorts": [
        {
                    "Host": "xxx",
          "Port": 80
        }
      ],
      "UpstreamPathTemplate": "/api/Document/{everything}",
      "UpstreamHttpMethod": [ "POST", "PUT", "GET", "DELETE" ]
    },
    {
      //Vision MiddleWare API
      "DownstreamPathTemplate": "/api/{everything}",
      "DownstreamScheme": "https",
      "DownstreamHostAndPorts": [
        {
                   "Host": "xxx",
          "Port": 443
        }
      ],
      "UpstreamPathTemplate": "/api/Vision/{everything}",
      "UpstreamHttpMethod": [ "POST", "PUT", "GET", "DELETE" ]
    },
    {
      //Third Parth API
      "DownstreamPathTemplate": "/api/{everything}",
      "DownstreamScheme": "http",
      "DownstreamHostAndPorts": [
        {
                    "Host": "xxx",
          "Port": 80
        }
      ],
      "UpstreamPathTemplate": "/api/ThirdPartyAPI/{everything}",
      "UpstreamHttpMethod": [ "POST", "PUT", "GET", "DELETE" ]
    },
    {
      //Referencing API
      "DownstreamPathTemplate": "/api/{everything}",
      "DownstreamScheme": "http",
      "DownstreamHostAndPorts": [
        {
                   "Host": "xxx",
          "Port": 80
        }
      ],
      "UpstreamPathTemplate": "/api/referencing/{everything}",
      "UpstreamHttpMethod": [ "POST", "PUT", "GET", "DELETE" ]
    },
    {
      //Rent Guarantee API
      "DownstreamPathTemplate": "/api/{everything}",
      "DownstreamScheme": "http",
      "DownstreamHostAndPorts": [
        {
                   "Host": "xxx",
          "Port": 80
        }
      ],
      "UpstreamPathTemplate": "/api/rentguarantee/{everything}",
      "UpstreamHttpMethod": [ "POST", "PUT", "GET", "DELETE" ]
    },
    {
      //Finance API
      "DownstreamPathTemplate": "/api/{everything}",
      "DownstreamScheme": "http",
      "DownstreamHostAndPorts": [
        {
                   "Host": "xxx",
          "Port": 80
        }
      ],
      "UpstreamPathTemplate": "/api/finance/{everything}",
      "UpstreamHttpMethod": [ "POST", "PUT", "GET", "DELETE" ]
    },
    {
      //UltimateLegal API
      "DownstreamPathTemplate": "/api/{everything}",
      "DownstreamScheme": "http",
      "DownstreamHostAndPorts": [
        {
                    "Host": "xxx",
          "Port": 80
        }
      ],
      "UpstreamPathTemplate": "/api/ultimatelegal/{everything}",
      "UpstreamHttpMethod": [ "POST", "PUT", "GET", "DELETE" ]
    },
    {
      //Configuration API
      "DownstreamPathTemplate": "/api/{everything}",
      "DownstreamScheme": "http",
      "DownstreamHostAndPorts": [
        {          "Host": "xxx",

          "Port": 80
        }
      ],
      "UpstreamPathTemplate": "/api/configuration/{everything}",
      "UpstreamHttpMethod": [ "POST", "PUT", "GET", "DELETE" ]
    },
    {
      //DirectToLandlord API
      "DownstreamPathTemplate": "/api/{everything}",
      "DownstreamScheme": "http",
      "DownstreamHostAndPorts": [
        {
                   "Host": "xxx",
          "Port": 80
        }
      ],
      "UpstreamPathTemplate": "/api/directtolandlord/{everything}",
      "UpstreamHttpMethod": [ "POST", "PUT", "GET", "DELETE" ]
    },
    {
      //Claim API
      "DownstreamPathTemplate": "/api/{everything}",
      "DownstreamScheme": "http",
      "DownstreamHostAndPorts": [
        {
                    "Host": "xxx",
          "Port": 80
        }
      ],
      "UpstreamPathTemplate": "/api/claim/{everything}",
      "UpstreamHttpMethod": [ "POST", "PUT", "GET", "DELETE" ]
    },
    {
      //Doc verification API
      "DownstreamPathTemplate": "/api/{everything}",
      "DownstreamScheme": "http",
      "DownstreamHostAndPorts": [
        {
                    "Host": "xxx",
          "Port": 80
        }
      ],
      "UpstreamPathTemplate": "/api/docverification/{everything}",
      "UpstreamHttpMethod": [ "POST", "PUT", "GET", "DELETE" ]
    },
    {
      //FinanceMS API
      "DownstreamPathTemplate": "/api/{everything}",
      "DownstreamScheme": "http",
      "DownstreamHostAndPorts": [
        {
                    "Host": "xxx",
          "Port": 80
        }
      ],
      "UpstreamPathTemplate": "/api/financems/{everything}",
      "UpstreamHttpMethod": [ "POST", "PUT", "GET", "DELETE" ]
    }
  ],

  "GlobalConfiguration": {
    "BaseUrl": "https://api-gateway.xxx.xxx.xxx"
  }
}

[raman-m]

Hello, Satvik!

I am using ocelot Version="24.0.0" in .net 7 microservices

Ocelot has ceased targeting the .NET 7 SDK as of version 24.0. The current target frameworks for Ocelot v24 are net8.0 and net9.0 ❗

---

builder.Configuration.AddJsonFile($"Ocelot/ocelot.{builder.Environment.EnvironmentName}.json", optional: false, reloadOnChange: true);
builder.Services.AddOcelot(builder.Configuration);
await app.UseOcelot();

Since version 24.0 you can reuse AddOcelot() method to add single configuration file:

Ocelot/samples/Basic/Program.cs

Line 9 in e78fe42

.AddOcelot(); // single ocelot.json file in read-only mode

Ocelot/src/Ocelot/DependencyInjection/ConfigurationBuilderExtensions.cs

Lines 218 to 219 in e78fe42

	public static IConfigurationBuilder AddOcelot(this IConfigurationBuilder builder,
	string primaryFile = null, bool? optional = null, bool? reloadOnChange = null) // optional injections

which is explained in the Getting Started doc.
So, you can write simply this 👇

builder.Configuration.AddOcelot($"Ocelot/ocelot.{builder.Environment.EnvironmentName}.json", false, true);
builder.Services.AddOcelot(builder.Configuration);
await app.UseOcelot();

---

sometime i am running into sudden memory spikes on aws ec2 , initially memory was near 8% that went to 16% somehow on ec2 and it not getting down during off business working hours

I do not believe this constitutes a spike; rather, it appears to be a typical memory increase resulting from the processing of demanding requests, such as handling large bodies or managing intensive loads a specific route.

---

it not getting down during off business working hours

Some frontend applications can establish long-lasting WebSocket connections. If you lack a WebSocket DownstreamScheme, a consistently high level of memory consumption suggests that your public-facing Ocelot gateway is handling constant traffic, which an entirely normal scenario.

during off business working hours

Understood! This indicates that Ocelot previously handled extensive requests, resulting in the allocation of large memory blocks, specifically ArrayPool objects. So, we don't manage TTL of those objects, and that's totally handled by .NET framework and garbage collector. (FYI @ggnaegi )
Furthermore, if the Caching feature is utilized, it is essential to configure suitable settings to ensure proper cache cleanup.

[satviktechie1986]

Sorry it was by mistake , we are using ocelot 19.0.2 with .net7 , now we are going to deploy ocelot with version 24.0 with .net 8 on production on this sunday .

[raman-m]

@satviktechie1986 You were using version 23.0 and you didn't have these problems? If so, then @raman-m it's not related to the array pool, which, by the way is returned....

Ocelot/src/Ocelot/Request/Mapper/StreamHttpContent.cs

Line 110 in e78fe42

ArrayPool<byte>.Shared.Return(buffer);

No, @ggnaegi! He said that he uses ver. 24, not v23.
That's why I've asked him again to describe full app tech spec: versions, environment etc.

[satviktechie1986]

so by changing ocelot to 24.0 version with .net 8 , will this be sort out ?

[raman-m]

Sorry it was by mistake, we are using Ocelot 19.0.2 with .NET 7, now we are going to deploy ocelot with version 24.0 with .net 8 on production on this sunday.

Understood! Unfortunately, we don't support older versions like v19.x—you’ll need to upgrade to v24.0 ❗ It also makes sense to use .NET 9, as it shares the same support period with .NET 8 under Microsoft's policy.
Version 24 is a stable release, so I recommend upgrading your apps sooner rather than later.

FYI

You should understand our upgrade, delivery, and support strategy—we don't provide backporting patches for old versions. Instead, we introduce features and fixes, immediately increasing the version and recommending that users update to the latest Ocelot version.
If your team encounters an issue in v24, please submit a new issue or start a new discussion.
Good luck with upgrading your Ocelot environment!

Additionally, I’m not looking to keep this discussion open, so I’ll be closing it now...

[satviktechie1986]

thanks for the update , anyway we are updating our ocelot version with 24.x with .net 8 , if we face any issue regarding performance will start a new issue/thread for discussion , happy days. :)