# Optimizing `LIMIT {offset}, {count}` Operation
__*LIMIT clause*__
__*Optimize LIMIT offset operation*__

+ Which part of the following execution plan are you most interested in? Why?
+ Try answering the following questions:
  + How many rows do you actually need? 
  + How many rows are processed per step?
  + Do you prefer to use **`{offset}`** to paginate? What is the alternative?
  + Do not access the rows you don't need
```
tidb> EXPLAIN SELECT name FROM planets ~!@LIMIT 8,1@!~;
+----------------------------+---------+-----------+---------------------------------+--------------------------------+
| id                         | estRows | task      | access object                   | operator info                  |
+----------------------------+---------+-----------+---------------------------------+--------------------------------+
| Limit_7                    | 1.00    | root      |                                 | offset:8, count:1              |
| └─IndexReader_12           | 9.00    | root      |                                 | index:Limit_11                 |
|   └─Limit_11               | 9.00    | cop[tikv] |                                 | offset:0, count:9              |
|     └─IndexFullScan_10     | 9.00    | cop[tikv] | table:planets, index:name(name) | keep order:false, stats:pseudo |
+----------------------------+---------+-----------+---------------------------------+--------------------------------+
4 rows in set (0.00 sec)
```

------------------------------------------------------------
Try answering the following questions.

1) How many lines do you actually need? 1
2) How many lines are processed in each step? 9, 9, 9, 1

For more information on execution plans, see: `https://docs.pingcap.com/tidb/stable/explain-overview`