New to site?


Lost password? (X)

Already have an account?


(X)

Presents

#CSHARPCON20

The C# Corner Annual Conference 2020 is a three-day annual event for software professionals and developers.

3
DAYS
72
SPEAKERS
65
SESSIONS

Magnus Mårtensson
Microsoft Regional Director, Azure MVP, CEO Loftysoft

Avirag Jain
Director & CTO R Systems

Mahesh Chand
Founder C# Corner, CEO Mindcracker

Chris Gali
CEO & Co-Founder Graphite

Subinder Khurana
Chief Architect StoryProcess, Founder NASSCOM DeepTech Club

Bryan Rishforth
Investor, Chairman Graphite

Bryn Everson
Director Biz Dev Graphite

Raj Tiwari
Digital Transformation Leader, Futurist and Visionary

Joseph Guadagno
Microsoft MVP, Lead Quicken Loans

Nikita Sachdev
Entrepreneur, Blockchain Enthusiast & Advisor, Social Media Influencer

Doug Wagner
COO & Founder Adapt Technical Group

Ritesh Modi
Architect, Senior Evangelist, Cloud Architect

Crystal Wenrick
Director Communications Mindcracker

Allen O’Neill
Microsoft MVP, Consulting Engineer/Architect

Praveen Kumar
CEO MCN Solutions

Chris Love
Founder Love2Dev, Microsoft MVP, Author

Sanjay Vyas
Microsoft Regional Director, Microsoft MVP, Founder & CEO SkillLabs Technologies

Veena Sarda
Deep Learning Consultant, Author

Sekhar Srinivasan
C# Corner MVP, Microsoft Certified Trainer, Pluralsight Author

Lalit Bansal
Founder & CEO - EIY SYS

Navdeep Garg
CEO Revinfotech

Prakash Tripathi
Tech Manager/Leader, Microsoft MVP, Blogger

Bhavna Jain
Breakthrough Consultant

Naveen Sharma
Enterprise Architect, Leadership Coach, Author

Vidya Vrat Agarwal
Principal Architect, Microsoft MVP, Author

Sheetal Agarwal
Founder Clownselors, Medical Clown, Trainer

Abhishek Kant
Founder GTM Catalyst

Vishnu Saran
Founder & CEO VoiceQube

Sandeep Soni
Founder & CEO Deccansoft, Microsoft Certified Trainer

Parveen Malik
AVP InfoSec & Vulnerability Management, Information Security Expert

Nitin Pandit
Microsoft MVP, Developer Evangelist, Author

Niloshima Srivastava
C# Corner MVP, Tech Architect, Trainer, Blogger

Bala Chirtsabesan
Senior Software Engineer at Microsoft, Author

Manoj Mittal
Sr. Technical Architect, C# Corner MVP, Author

Chandni Di
Co-Founder Voice of Slum

Vithal Wadje
Technical Lead, Microsoft MVP, Author

Shivam Ahuja
Founder SkillCircle, Business Mentor

Chervine Bhiwoo
Solution Architect, Microsoft MVP, Author

Saurabh Jain
Vice President Paytm, Founder Fun2Do Labs, Author

Vinay Solanki
Head IoT at Lenovo, Founder IoT-NCR

Anshu kumari
Founder Blockchainkids, Inventor, Trainer

Amit Singal
CEO Startup Buddy

Dev Pratap
Co-Founder & CEO Voice of Slum

Amey Vartak
Technology Consultant, Full Stack Developer, C# Corner MVP, Author

Viswanatha Swamy
Principal Software Engineer, C# Corner MVP, Author

Sanket Verma
Research Engineer @ Ballistics (Forensics) and Chair, PyData Delhi

Sourabh Somani
Lead Developer, Microsoft MVP, Author

Abhishek Mishra
Software Architect, C# Corner MVP, Author

Siddharth Vaghasia
Technical Consultant, C# Corner MVP, Blogger

Bassam Alugili
Senior Software Specialist, Database Expert

S Ravi Kumar
Solution Architect, C# Corner MVP, Author

Sundaram Subramanian
Full Stack Developer, C# Corner MVP, Speaker

Deepesh Somani
Solution Architect, Microsoft MVP, Author

Debasis Saha
Technical Project Manager, C# Corner MVP, Blogger, Author

Vipul Jain
Software Architect, C# Corner MVP, Author

Akshay Patel
Technical Architect, Microsoft Certified Trainer, C# Corner MVP, Author

Stephen Simon
RPA Developer, Evangelist, Author

Vivek Sharma
Founder Kingster636, AR/VR Specialist

Jeetendra Gund
Technical Lead, C# Corner MVP, Author

Sujal Beniwal
AI Enthusiast, Student

M Viknaraj
Microsoft MVP, Azure Architect, Author

Prasham Sabadra
Software Architect, C# Corner MVP, Trainer, Author

Aakash Maurya
Senior Developer, C# Corner MVP, Speaker

Ankit Sharma
Senior Software Engineer, C# Corner MVP, Author

Mangesh Gaherwar
Team Lead, C# Corner MVP, Author

Viral Jain
Technical Consultant, C# Corner MVP, Author

Bhasker Das
Solution Architect, Evangelist

Manish Dwivedi
Associate Project Manager

Ck Nitin
Programmer, Author

Rohit Gupta
Technical Trainer, Author

Manish Tewatia
Full-stack Marketer, UX Designer

Bhavya Gaur
Technical Illustrator

Rohit Tomar
SEO/SMO Expert

Web Track

Cloud & Data Track

Dev Track

8am-9am

Registration & Breakfast

9am-10am

Future of Desktop Apps with JS (ElectronJs)

Nitin Pandit

Building Serverless Microservices Using Microsoft Azure

Vithal Wadje

Innovating RPA: A Robot for Every Person

Stephen Simon

10am-11am

Managing Cloud Storage Accounts using Logic Apps

Viknaraj Manogararajah

Data visualization using Python

Sekhar Srinivasan

Going Cross platform with AR Foundation

Vivek Sharma

11am-12pm

Keynote

12pm-1pm

Managing your Azure dependencies in ASP.NET Core apps using VS

Bala Chirtsabesan

Securing Applications on Intelligent Azure

Abhishek Mishra

Getting started with Blazor the Framework of Future

S Ravi Kumar

1pm-2pm

Lunch

2pm-2:45pm

Build Progressive Web Apps using Angular 9

Debasis Saha

Build and deploy to any platform using Azure DevOps

Chervine Bhiwoo

Deep Dive in Azure Service Bus

Akshay Patel

2:45pm-3:45pm

Build a Native Mobile Application using React Native and JavaScript

Joseph Guadagno

Making sense of Web Job, Web Job SDK and Functions in Azure

Prakash Tripathi

CloudFront Distribution in AWS

Viral Jain

3:45pm-4pm

Tea Break

4pm-4:30pm

Introduction to PowerBI

Aakash Maurya

Build Advanced SPFx solutions with React and Graph API

Siddharth Vaghasia

Build Business Intelligence Analyst (BIA) Skills

Sundaram Subramanian

4:30pm-5pm

Deep dive of Power Platform – AI BUILDER

Prasham Sabadra

Panel 1

What's new in SharePoint development

Vipul Jain

5pm-5:30pm

Build a SSO (Single Sign On) based Native JavaScript application with Microsoft Identity within 10 minutes

Manoj Mittal

Panel 2

Applications and working of AI

Veena Sarda

5:30pm-6pm

Deploying serverless API's with .Net core 3.0 on AWS & Azure

Amey Vartak

Panel 3

Blockchain with .NET Core (Ark)

Anshu Kumari

6pm-6:30pm

Closing Note & Prize Distribution

Dev Track

Cloud Track

Architecture Track

Emerging Tech Track

8am-9am

Registration & Breakfast

9am-10am

Creating Full-Stack Web Apps Using Server-Side Blazor

Ankit Sharma

Real time face recognition with MS Cognitive Services

Niloshima Srivastava

Building Scalable APIs with GraphQL

Jeetendra Gund

Future of development with AI and Blockchain

Navdeep Garg

10am-11am

Debugging Tips and Tricks with Visual Studio 2019

Joseph Guadagno

Azure Containers

Abhishek Kant

Enterprise Architecture

Naveen Sharma

Bot Framework - learn it fast and look like a boss!

Allen O’Neill

11am-12:30pm

Keynote

12:30pm-1:30pm

.Net Core & C# 8 Performance

David McCarter

Working with Azure kubernetes services

Ritesh Modi

Becoming an Architect

Vidyavrat Agarwal

Why Techies Need to Learn Product Management

Saurabh Jain

1:30pm-2:30pm

Lunch

2:30pm-3:30pm

Build a rules engine in .Net Core

Sanjay Vyas

Building CI and CD Pipeline using Azure DevOps

Sandeep Soni

Entity Framework Core - Tips and Tricks, Performance Optimization, and Tuning

Bassam Alugili

Hacking your way into Data Science

Sanket Verma

3:30-4:15pm

Speed up your .Net Core Website

Sourabh Somani

Azure

Magnus Mårtensson

Demystifying Open Distro for Elasticsearch

Suman Debnath

Future of Data

Shivam Ahuja

4:15pm-4:30pm

Tea Break

4:30pm-5:15pm

gRPC with C# and .Net Core

Mangesh Gaherwar

Panel 1

Essentials of Cloud security

Parveen Malik

Power platform and Dynamics 365

Deepesh Somani

5:15pm-6pm

Microservices - the gRPC Way

Viswanatha Swamy

Panel 2

Reserved

Reserved

6pm-6:30pm

Closing Note & Prize Distribution

Using Azure Load Testing to stress test .NET applications

A .NET application can perform well during development and still struggle when real users arrive in large numbers. A sudden product launch, seasonal campaign, data import, or business-to-business integration may create traffic patterns that ordinary functional tests never reproduce. Load testing reveals how an application behaves when requests, connections, background jobs, and database operations compete for resources.

Azure Load Testing provides a managed way to generate traffic and observe application behavior at scale. It can work with ASP.NET Core APIs, MVC applications, microservices, and services deployed across Azure or connected environments. By combining a realistic workload with Azure Monitor and Application Insights, development teams can connect user-facing symptoms to infrastructure and code-level causes.

For software professionals attending a technology conference focused on .NET, Azure, cloud computing, DevOps, and data, this subject brings several disciplines together. Performance engineering is not a final checkpoint. It is a repeatable part of application delivery that helps teams make better architecture, capacity, and release decisions.

Why performance testing belongs in the delivery cycle

Stress testing pushes an application beyond its expected operating range to discover its breaking point. Load testing usually validates behavior at a planned level of concurrency, while stress testing continues increasing demand until response times degrade, errors rise, or supporting services reach their limits. Both approaches are valuable because production traffic rarely remains perfectly stable.

A .NET workload can fail in several places. Thread pool starvation may delay requests even when CPU usage appears moderate. A connection pool can become exhausted while application servers remain healthy. Slow Entity Framework Core queries may increase request duration and keep more workers occupied. External APIs, queues, caches, and storage accounts can introduce bottlenecks that are invisible in a developer workstation test.

Running tests throughout the development lifecycle helps identify these issues before they become incidents. A baseline test can run on every major release, while a larger capacity test can run before a public launch. Teams should preserve test scripts, environment settings, dashboards, and acceptance thresholds in source control so that results remain comparable over time.

Preparing a .NET application for realistic traffic

A useful test begins with a clear model of user behavior. List the transactions that matter to customers, such as signing in, searching, loading a dashboard, submitting an order, uploading a document, or retrieving a report. Record the approximate frequency of each action, the expected payload size, and the sequence in which calls occur. A script that sends the same request repeatedly may produce impressive request counts but provide little insight into actual performance.

Azure Load Testing can execute Apache JMeter-based scenarios and distribute traffic from managed test engines. For a .NET API, the script should include authentication flows, headers, correlation identifiers, realistic data, and parameterization. Test accounts and data sets need enough variation to avoid unrealistic cache hits or database contention patterns. Secrets should be supplied through secure configuration rather than embedded in the test plan.

The target environment should resemble production in the areas that influence performance. Match app service plans, container resources, database tiers, network paths, caching settings, and autoscale rules as closely as practical. Teams modernizing older systems can also review legacy .NET migration considerations, since framework changes, hosting models, and cloud service integrations may alter the performance profile.

Connecting load generation with observability

A load test produces value when it explains why the system behaves as it does. Configure Application Insights to capture request duration, dependency calls, failure rates, availability, and representative traces. Azure Monitor metrics can add visibility into CPU, memory, network throughput, storage latency, database operations, and platform-level throttling. Distributed tracing is especially useful when one user action crosses several microservices.

Before starting, define performance objectives. Examples include keeping the 95th percentile API response below a specified duration, maintaining an error rate under a fixed threshold, or completing a background workflow within an agreed service-level objective. Percentiles are more informative than averages because a small group of very slow requests can affect real users even when the average looks healthy.

Correlation between the test timeline and telemetry matters. Mark the beginning of warm-up, steady-state traffic, ramp-up, peak load, and recovery. Compare server response time with total user-perceived latency, since network delay and client-side processing may create a different experience. Review logs after the run, but avoid enabling excessive diagnostic detail in a way that changes the behavior being measured.

Area Signals to monitor Warning signs Useful follow-up
ASP.NET Core API Request duration, failed requests, HTTP status codes Rising latency or 5xx responses Inspect middleware, thread usage, and slow endpoints
Application servers CPU, memory, active requests, GC activity Saturated workers or frequent garbage collection Tune resources, code paths, or scaling rules
Database DTU or vCore usage, locks, query duration, connections Blocking, pool exhaustion, slow reads Review indexes, queries, pooling, and tier size
Dependencies Dependency duration and failure rate Timeouts from APIs, queues, or storage Add resilience, caching, retries, or capacity
Platform scaling Instance count, scale-out delay, request distribution Late or uneven scaling Adjust rules, cooldowns, and minimum instances
Client experience End-to-end latency and page timing Slow rendering despite healthy servers Optimize payloads, browser work, and static assets

Designing a safe and effective stress scenario

A progressive ramp is safer than an immediate traffic spike. Begin with a warm-up period that allows application startup, caches, JIT compilation, and connection pools to settle. Increase virtual users or request rates in controlled steps, holding each level long enough to observe stable behavior. Continue until the system reaches its planned limit or a predefined stop condition is met.

Stress tests should have clear guardrails. Establish maximum request rates, spending limits, test duration, and automatic cancellation rules. Do not direct destructive operations at production data unless the scenario has been specifically approved and isolated. A staging environment with production-like data volume is often preferable, but personally identifiable information must be removed or protected.

Failure behavior is part of the result. Check whether the application returns useful status codes, preserves data integrity, retries safely, and recovers after demand decreases. For asynchronous .NET workloads, monitor queue depth and processing delay after the test ends. An API may appear healthy while background workers are still accumulating a backlog that will affect users later.

Reading results and finding the bottleneck

Start analysis with the shape of the graphs rather than a single maximum number. A gradual increase in latency as concurrency rises may indicate resource saturation. A sudden jump can point to a threshold such as connection limits, a queue boundary, a rate limit, or an autoscale event. Compare the point where errors begin with the point where response times first become unacceptable.

Investigate the slowest transactions and their dependencies. An endpoint that spends most of its time waiting for SQL Server needs a different remedy from one consuming CPU during JSON serialization. For Entity Framework Core, examine generated SQL, query plans, eager loading, indexes, and result sizes. For ASP.NET Core, review synchronous blocking, excessive allocations, serialization settings, and long-running work inside request handlers.

Fixes should be tested independently where possible. Increasing the App Service plan may hide inefficient queries without solving them. Adding retries can increase load during an outage if backoff and limits are poorly designed. Caching can reduce database pressure, but stale data rules and cache invalidation must be explicit. After each significant change, repeat the same scenario and compare against the original baseline.

A practical test readiness checklist

Teams get more reliable results when performance testing is treated as an engineering process rather than a one-time tool exercise. The following practices create a solid foundation for a .NET workload:

  • Define target concurrency, request mix, latency percentiles, error budgets, and recovery expectations.
  • Build realistic data, authentication, payload, and user-session behavior into the test script.
  • Connect Azure Load Testing with Application Insights and Azure Monitor before the first serious run.
  • Isolate test accounts, protect secrets, and set cost, duration, and traffic guardrails.
  • Store scripts and configuration in source control, then compare every major run with a known baseline.

The test environment should also include operational readiness. Notify teams responsible for databases, networking, identity, and downstream services before a high-volume run. Confirm that alerts are meaningful and that on-call staff can distinguish planned test traffic from an unplanned incident. Capture the final workload model and capacity result so it can inform architecture reviews and release planning.

Turning performance findings into release decisions

A test report should state whether the application met its objectives, where it reached capacity, and what assumptions shaped the result. Include the workload profile, test duration, deployment version, infrastructure size, observed bottlenecks, and recommended actions. Screenshots alone are insufficient; preserve raw metrics and links to the relevant monitoring views when possible.

Capacity planning becomes more useful when it expresses business impact. Instead of saying that a service handled 2,000 virtual users, document the corresponding transactions per minute, expected revenue event, or customer activity. Record the cost of running at that capacity and the scaling time required to handle a surge. This information supports decisions about reserved capacity, autoscaling, caching, queue-based processing, and database investment.

Azure Load Testing fits naturally into a DevOps pipeline. A smaller smoke-load test can run against each deployment, while a full stress test can run nightly or before major launches. Set thresholds that fail the pipeline when performance regresses, but allow teams to review intentional changes such as a new feature with heavier processing. Over time, historical results reveal whether the system is improving, drifting, or approaching an architectural limit.

Make performance a repeatable engineering practice

Begin with one important .NET user journey, a measurable target, and a small representative workload. Instrument the application, run a baseline, increase demand gradually, and investigate the first meaningful signs of degradation. Then turn the scenario into an automated test that can run whenever the application or its cloud dependencies change.

Use the resulting evidence to prioritize code improvements, infrastructure changes, and operational safeguards. Set up an Azure Load Testing experiment for your next release, compare its results with a baseline, and carry the findings into the team’s next design and delivery discussion.

The Leela Ambience Convention Hotel

1, CBD, Maharaj Surajmal Road, Near Yamuna Sports Complex, Delhi, 110032

KNOW MORE

GENERAL QUERIES


Manish Tewatia

+91-9718-431-042

TICKET QUERIES


Atul Gupta

+91-9910-125-804