Skip to content

Random microbenchmarks for some patterns that I came across in my daily life as a .net dev

License

Notifications You must be signed in to change notification settings

szaboopeeter/netcore-microbenches

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

4 Commits
 
 
 
 
 
 
 
 

Repository files navigation

.Net Core Micro-Benchmark Scenarios

Motivation

During my everyday life, be that as part of my dayjob, open-source projects, consulting, or simple Stackoverflow question, I tend to run into creative code solutions, where the people with (most of the time) good intentions end up writing something that performs terribly.

While I agree with the arguments against premature optimization and that time spent micro-optimizing code outside of hot-paths can usually be better spent, I don't really consider these cases as micro-optimizing. You could probably provide even better performing alternatives (feel free to do so), I'm mostly trying to show that in some cases even the most intuitive solution will perform better than the one considered "creative" by their authors.

Table of contents

1 - Mapping objects (using a JSON serializer)

About

Random microbenchmarks for some patterns that I came across in my daily life as a .net dev

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages