When each millisecond counts?
summary
yr.no serves ~8–10 million weekly users and ~100k requests/min so every millisecond matters; load tests with k6 show .NET Core 3 runs far more stably than Core 2 under stress. JSON: Newtonsoft wins on small payloads, System.Text.Json only outperforms at very large payloads. Linux containers beat Windows for API stability. Geospatial query timings: SQL Server ~700 ms, Cosmos DB ~300 ms but costly, PostgreSQL 250–440 ms. Dapper naive inserts take ~4s vs Dapper bulk insert ~100 ms. HashSet lookup cuts 380 ms to ~10 ms for 10k items; avoid blind EF use.
AI-written summary · about
chapters (4)
- 0:00When each millisecond counts
- 0:51When 1ms actually makes a difference
- 4:23Linux is better than Windows
- 8:173. Code and algorithms
related talks
37mRock Your Code Code and App Performance for Microsoft .Net
32mBuilding .NET software with focus on performance and scalability
50mHow I have improved the Database performance from 5 seconds to 1 millisecond
45mGetting the Most from NoSQL in the Cloud with Azure Cosmos DB
01h 00mRock Your Code: Code & App Performance for Microsoft .NET
01h 05mCommon mistakes in EF Core
46mHigh Performance .NET
01h 03mAzure Cosmos DB - The Best NoSQL Database You're Probably Not Using (Yet)