Are you of the opinion that performant code is poorly readable code? Do you believe that performant code can only be written retrospectively? Or do you think that only a cache can save performance? Then attend this session and be amazed.
Here you will find tips for your daily work with .NET. Easy to follow and guaranteed to write faster and still readable code. We will also look at how to make (supposedly) performant code even faster. This type of optimization requires performance measurements and makes the work more time-consuming? In most cases, yes. Because often only a series of measurements can show which variant is better. Fortunately, there are also tips for non-everyday work. Also with a guarantee for better performing code.
Overall, we are operating at a very high level here. Comparable to Formula 1 when it comes to car racing. We are talking about optimizations in the millisecond or microsecond range when measured individually. In total, however, the savings can be much higher. It all depends on how often the code is run. Two small calculation examples: If you save 1 ms on one call, this amounts to almost 17 seconds on 1 million calls. Or: If you save 10 microseconds per call, this also amounts to almost 17 seconds for 100 million calls. And 100 million calls can quickly add up, for example when cross-producing two collections with 10,000 entries each.
In times of cloud computing, big data and AI, performance is playing an increasingly important role. The faster and more resource-efficient an application achieves the same result, the greater the gain in terms of time and money.