md-table-pagination Page selector with 'big data'

I’ve been playing around with this module and server side pagination of ‘big data’ (big data = ~70,000 records - Not that big), and have noticed that within the module ‘md-table-pagination.html’ where the <md-option> for each page number is being generated is causing CPU bottleneck.

https://github.com/daniel-nagy/md-data-table/blob/1cef4dbacd977110ed70ccd74609f8228772b64a/dist/md-data-table.js#L1292

angular.module('md-table-pagination.html', []).run(['$templateCache', function($templateCache) {
  $templateCache.put('md-table-pagination.html',
     //Excerpt
    '<md-select class="md-table-select" ng-show="showPageSelect()" ng-model="page" md-container-class="md-pagination-select" ng-change="onPageChange()" aria-label="Page">\n' +
    '  <md-option ng-repeat="num in range(pages()) track by $index" ng-value="$index + 1">{{$index + 1}}</md-option>\n' +
    '</md-select>\n' +

Namely: ng-repeat="num in range(pages()) track by $index" 

So the higher the pages() return value, the more md-option elements obviously, and it just becomes really sluggish. Technically not a fault of md-data-table, more-so angular material however it does seem logical to have some sort of page range algorithm or some logical UX to handle this part logically when there’s an excessive amount of pages.

tl;dr: Page selector in <md-table-pagination> causes bottleneck when there’s lots of pages.

[daniel-nagy]

Hi all, in v0.10.0 the page dropdown uses virtualization.

[MikeSam]

@Mechzeit @nevernet Is latest version v0.10.0 solved your issue with pagination big tables? I have the same issue now with table > 2 500 000 rows.