Hello Dennis Gundersen,
About the slow filtering, it seems like in order to do the filtering you are using some LINQ query on a IQueryable instance and this results in a request to the database probably on every key stroke (depends on how the filtering is implemented). If this is the case it is no surprise that filtering is slow.
In order to have the filtering perform as expected, you will have to load the data in a collection (for example a list) only one time and then use this for the filtering functionality so that you do not have requests to the database while filtering. Keeping this list in memory should not be an issue with 7000 items.
Regarding the other issue that you mention, I am not sure that I completely understand what you mean with "the whole list is loaded every time I add a new record that includes a component". Could you please share more details about your case. A sample project that demonstrates the issue will be perfect.
I hope this helps. Do not hesitate to write again if you have more questions.
All the best,
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Public Issue Tracking
system and vote to affect the priority of the items.