All geek questions in one place

Comparison of i4o and PLINQ for large collections

I have a question for those who have experience with i4o or PLINQ. I have a large collection of objects (about 400 KB) needed for the request. The logic is very simple and straightforward. For example, there is a collection of Person objects, I need to find faces mapped to the same firstName, lastName, datebirth or first first name FirstName / lastname, etc. This is just a time consuming process using LINQ to Object.

I am wondering if i4o (http://www.codeplex.com/i4o )

or PLINQ can help improve query performance. Which one is better? And if there is some kind of approach.

Thanks!

+3
source share
3 answers

With 400k objects, I wonder if the database would be a more suitable answer (either in the process or outside the process). This then abstracts the process of creating the index. In particular, any database will support several different indexes on different columns (columns), making queries quoted by all very convenient without the need for coding specifically for each (just let the query optimizer worry about this).

Working with it in memory may be valid, but you can (with vanilla.NET) do a lot more manual index management. The sounds of this i4o are definitely worth exploring, but I don't have any existing comparison data.

+5
source

i4o: linq , .

PLinq: .

- , , , i4o .

+3

i4o, PLINQ.

, , , ( ) .

PLINQ , . , .

i4o , , , .

- .

0

Source: https://habr.com/ru/post/1704049/

More articles:


All Articles