Radhakrishnan Perumal

  10 ASP.NET Core Performance Tweaks Every Dev Should Know A.Radhakrishnan  Most ASP.NET Core apps don’t need a full rewrite, They need these 🔟 micro-tweaks: 1. Use Minimal APIs for Lightweight Endpoints Ditch MVC where it’s overkill. Less overhead, faster routing. 2. Avoid .ToList() Too Early  Let EF Core compose the query — don’t force it prematurely. 3. Enable Response Caching  Static content? Cache it and save the CPU for real work. 4. Use AsNoTracking() for Read-Only Queries  Need blazing read speed? Stop EF from tracking changes you don't need. 5. Trim Middleware  Each middleware = overhead. Audit your pipeline. 6. Compress Responses (Gzip/Brotli)  Small payload = faster load. Your API will thank you. 7. Benchmark with BenchmarkDotNet  Guessing is for gamblers. Profile your bottlenecks. 8. Pool DbContext in High-Load Apps  DbContext pooling = fewer allocations = faster throughput. 9. Tune Kestrel Server Settings  Thread count, lim...

 Recall ai reduced AWS bill by >$1,000,000 / year  Reducing bots CPU usage by up to 50% doing 👇 Problem They identified majority of CPU time was spent in two "copy memory" functions 1. __memmove_avx_unaligned_erms  2. __memcpy_avx_unaligned_erms Biggest callers of these functions are, 1. Python WebSocket that was receiving the data 2. Chromium's WebSocket that was sending the data Expensive sockets - Single 1080p 30fps video stream, in uncompressed I420 format = 93.312 MB/s - Monitoring showed that at scale, the p99 bot receives 150MB/s of video data Solution - Shared Memory was implemented simultaneously accessed by multiple processes at a time  - Chromium writes to a block of memory, which is read directly by video encoder with no copying - Ring buffer was chosen as high level transport design Ring Buffer implementation Three pointers on Ring buffer - Write pointer: the next address to write to - Peek pointer: the address of the next frame to read - Read pointe...

       𝗦𝘆𝘀𝘁𝗲𝗺 𝗗𝗲𝘀𝗶𝗴𝗻 - 𝗥𝗘𝗦𝗧 𝗔𝗣𝗜 𝗕𝗲𝘀𝘁 𝗣𝗿𝗮𝗰𝘁𝗶𝗰𝗲𝘀             Article By: Radhakrishnan A Perumal   A REST API defines a set of rules that developers should follow when creating APIs. While designing REST APIs seems straightforward, there are some common mistakes you should avoid in interviews👇 𝟭) 𝗨𝘀𝗶𝗻𝗴 𝘃𝗲𝗿𝗯𝘀 𝗶𝗻 𝗨𝗥𝗟𝘀 The endpoint URL should represent a resource (a noun), not an action (a verb). The HTTP method already indicates the action to be performed. ❌ GET /getAllBooks ❌ POST /createNewBook ✅ GET /books ✅ POST /books 𝟮) 𝗡𝗼𝘁 𝗨𝘀𝗶𝗻𝗴 𝗔𝗽𝗽𝗿𝗼𝗽𝗿𝗶𝗮𝘁𝗲 𝗛𝗧𝗧𝗣 𝗠𝗲𝘁𝗵𝗼𝗱𝘀 Using the appropriate HTTP method makes your API intuitive. ↳ GET = retrieve data ↳ POST = create new resources ↳ PUT = replace the entire resource with a new representation provided in the request body. ↳ PATCH = Used to apply partial modifications to a resource ...

  𝗙𝗿𝗼𝗺 𝗖𝗹𝗮𝘀𝘀𝗶𝗰 𝗦𝘄𝗶𝘁𝗰𝗵 𝘁𝗼 𝗦𝘄𝗶𝘁𝗰𝗵 𝗘𝘅𝗽𝗿𝗲𝘀𝘀𝗶𝗼𝗻   Article By: Radhakrishnan A Perumal                                                                              Clean up old code with modern C# If you're still using old-style switch statements with repetitive case blocks and breaks, it's time for an upgrade. C# 8.0 introduced switch expressions, a modern, concise, and more readable alternative. They eliminate boilerplate and make your logic feel more declarative and elegant. 𝗡𝗼 𝗺𝗼𝗿𝗲: • Long chains of case blocks • Repeating return statements • Manual break management 𝗜𝗻𝘀𝘁𝗲𝗮𝗱, 𝘆𝗼𝘂 𝗴𝗲𝘁: • Compact syntax • Built-in pattern matching • Better type inference • Improved readability Whether you’re ret...