better handling of relations with many records

having some 15000 records in a m2m relation and not specifying a good enough search criteria creates (too) high loads on server, network and client
suggestions
* stop button - the user should be able to interrupt the process and go to refine the search
* auto stop - after 3-5 seconds or the usual 80 records the system asks
** message "already found xxx records" - do you want to
*** continue (does usually not make much sense to transfer some 1000 records)
*** refine your search

m2o limit the number of records to 80 (or whatever is defined somewhere ...)
but miss next/previous button

and we have discussed similar matter already for o2m widgets.

Some more suggestions (lost in the old wiki)
having mobile users ans SAAS in mind
- reduce bandwidth usage
* fetch only records if number of records/results < one or 2 screen full
** else: "please refine your search"
* sort records
** must not sort "id"
** sort field(s) must be visible