Skip to main content

Switch vs Dictionary

Revin cu cateva informatii suplimentare pe tema switch vs dictionary ca o continuare a postului

Putem-sa-inlocuim-switch-case

In cazul in care avem un switch simplu care nu are nevoie sa sara de la un case la altul, codul IL care se genereaza in spate o sa fie foarte simplu si rapid. Se genereaza ceva de genul:

IL_0002: ldloc.0
IL_0003: switch (
IL_0016,
IL_001e,
IL_0026)
IL_0014: br.s IL_002e

Dar cand de la un case se sare la un alt case deja IL generat se complica si ar fi bine sa se faca un review la cod. Codul generat mai jos este pentru un switch care are cateva case-uri goale( au fost adaugate doar pentru ca sa avem un cod cat mai readeable) si un case ce nu are break. In cazul acesta, pierderea de performanta este de aproape 50%. Sursa: http://weblogs.asp.net/justin_rogers/archive/2004/03/25/95806.aspx

IL_0002: ldloc.0
IL_0003: switch (
IL_002e,
IL_0036,
IL_003e,
IL_0056,
IL_0056,
IL_0056,
IL_0056,
IL_0046,
IL_004e)
IL_002c: br.s IL_0056

Pentru cazul acesta putem folosii dictionarul cu success. Pe partea de value la dictionar, putem folosii o lista de functii, care o sa fie apelate pe rand, cand o sa avem nevoie de un switch fara break. In cazul unor flow-uri mai complexe ar trebui sa ne implementam un mecanism de workflow.

Recomandari pentru switch:

  • blocuri compacte, fiecare case sa aiba break;
  • expresia comparata sa fie de tip enum sau cu int cu valori fixe( fara intervale de genul: 1 .. 20 si 40 .. 100);
  • char in loc de string-uri( si enum in loc de char);

Daca aveti nevoie de performanta, iar continutul din case nu este complex( nu trebuie sa se apeleze si alte blocuri case la randul sau), switch-ul o sa fie mult mai performant. Dar atentie, in cazul in care in expresia de la switch avem string, folosirea unui dictionar, hashtable sau a unui switch o sa aibe rezultate asemanatoare in IL. Switch-ul o sa fie generat pentru expresii de tip string ca si un hashtable.

Comments

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...