Proposal: md-select direct options data wiring for better startup time

[mbellezi]

Bug, feature request, or proposal:

Proposal

What is the expected behavior?

For more the one hundred itens, md-select should not be slow.

What is the current behavior?

For 200 itens, the md-select startup time is 150ms on desktop and nearly 1s on mobile. Even with AOT is slow.

What are the steps to reproduce?

Create a md-select with 200 itens or more.

Is there anything else we should know?

The md-select options could be wired directly using one @input that takes one array of label/value objects. This could be used to speedup startup as one do not have process and iterate through the md-option array.

[kara]

The select needs virtual repeat for long lists, which still hasn't been implemented. That should improve perf: #823. Closing this one as a dupe to track in the other one.

[mbellezi]

I understand but there are two phases here. One is instantiate and parse all md-option components and the other is the render itself.
I'm proposing to bypass this first phase when you want a simple Label/value list. Why do all the processing to build a list of label/value pairs when you could (optionally) pass it in as a @input?
In my opinion, there is no need to always emulate the select tag behavior (option tags).

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}