Skip to main content

Care este cea mai rapida metoda pentru a obtine index-ul unui element din IEnumerable

De cate ori nu v-ati lovit de acest caz? Sa aveti un obiect de tip enumerable si sa fim nevoiti sa obtineti indexul unui element.
Exista mai multe metode pentru a rezolva aceasta problema, cea mai simpla din ele este:
obj.ToList().FindIndex( x => x =="Blog" )
Pentru cazul in care am cautat elementul care are valoarea "Blog".
Daca ne punem problema vitezei putem sa scriem noi o metoda popie:
public static int FindIndex<T>(this IEnumerable<T> elemente, Predicate<T> conditie)
{
int index = 0;
foreach (var item in elemente)
{
if (conditie(item))
{
return index;
}
index++;
}
return -1;
}
Prima optiune ne sperie putin din cauta la ToList(). Ne punem problema performantei, am prefera parca sa nu folosim ToList() si sa mergem pe metoda scrisa de noi.
elemente.Select((item, index) => new { item, index })
.Where(p => p.item == "Blog")
.Select(p => p.index + 1)
.FirstOrDefault() - 1;
Ce am facut mai sus? Nimic complicat, am obtinut toate elementele din enumeratie sub forma (element, index). Daca nu stiati Select-ul ne permite acest lucru, ne poate fi de ajutor aceasta metoda in multe alte situatii. Apoi am selectat doar elementele care respecta conditia, iar apoi am selectat index-ul la acest element. FistOrDefault ne garanteaza ca acest algoritm se va oprii dupa ce a gasit primul element care indeplineste conditia data. M-am folosit de +1 si -1 la Select si la FirstOrDefault pentru a putea avea rezultatul -1 cand nu se gaseste nici un element in enumeratie ce sa indeplineasca conditia data.
Mai exista si alte mecanisme, folosind TakeWhile.
Problema nu este neaparat cum, ci care este mai optim mecanism.
Desii e greu de crezut cel mai rapid mecanism este ToList().FistIndex(). Se pare ca nu intoadeauna un cod scris de mana este mai rapid ca si un API default oferit de catre .NET, chiar daca vorbim de LINQ.

Comments

  1. Interesant - ai facut niste masuratori ca sa vezi cu cat e mai rapida metoda ce foloseste LINQ/Select ?
    (la prima metoda, nu mi-e prea clar de ce era nevoie sa se foloseasca ToList())

    ReplyDelete
  2. Problema e ca query-ul scris cu LINQ e gresit. Punand clauza Select((item, index) => new { item, index }) prima, am invalidat tot lazy-loading-ul care il ofera LINQ.
    Corect ar fi:
    elemente.Where(p => p.item == "Blog")
    .Select((item, index) => new { item, index })
    .FirstOrDefault();

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP