Mysql descending Indexes performance check

The official documentation of mysql descending indexes says a bit about performance , so I was curious about how much performance will it change if the index is used in a right way ASC or DESC.
https://dev.mysql.com/doc/refman/8.0/en/descending-indexes.html
<b>Part1</b>
・mysql --version
　mysql  Ver 8.0.21 for osx10.13 on x86_64 (Homebrew)
Let's go throw some basics first,
While adding an Indexes on a table, by default the order BY is 'ASC'
let's see the table details for reference;
・mysql> DESCRIBE chair1;
![describechair1.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/475245/ce2ebe17-d75d-30c4-f5b9-d0f213f991fa.png)
![count.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/475245/591a1687-2cbe-78a5-d076-027ff95e6256.png)
let's check the indexes on our table first and add and drop indexes later as per this documentations check,
mysql> SHOW INDEXES FROM chair1;
![showindexes1.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/475245/46682e49-9b66-f267-bd56-99f54d7fefc8.png)
Now I will add a popularity index, let's check the collation afterwards 
→ Alter table chair1 add key (popularity); ←by default it will be an index by ASC
![index2.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/475245/f6890aca-9384-5cd2-8853-141589db9b9a.png)
let's check by executing a simple query
・　mysql> select * from chair1 order by popularity;
execution result:
![defaultorder.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/475245/0cacd508-ec79-11b7-c35a-0c66e4fcd094.png)
・execute another query with order by DESC
　mysql> select * from chair1 order by popularity DESC;
execution result:
![descorder.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/475245/8b25faf4-617b-dc1c-a9a2-d8d4e35088c8.png)
In this cases, there is not that much performance difference in both queries; but depending upon the query may be the performance difference can be slightly high.

let's make the index DESC then execute the above queries;
・　mysql> Alter table chair1 add key (popularity DESC);
![ADDDescIndex.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/475245/8deea75d-8824-2298-d5b9-0c475e434473.png)
Now the collation is 'D' for popularity index, 
・　mysql> select * from chair1 order by popularity;　←　ASC by default
![ASC15.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/475245/93a49c8c-47ad-5733-5f10-1e70fb02140d.png)
・mysql> select * from chair1 order by popularity DESC;　←changed order by same as the index DESC
![desc12.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/475245/8db767b0-d44c-b6bb-6c6f-87605461336f.png)
A minor ignorable performance difference between both the queries.I feel like, for simple queries it doesn't change much but once the query become more complex with many condition and clauses then DESC index can be helpful that time.
Just to try I added some where clause on primary key and tried with order by ASC and DESC respectively.
![bothIndex.png](https://qiita-image-store.s3.ap-northeast-1.amazonaws.com/0/475245/d65deacb-6be9-6d27-0e50-f2eb15ad0d3c.png)
↑Target rows 14414 in both cases with explain.

<b>Part2:</b>
Descending Indexes doesn't work with mysql version older then 8 ,so later on I will try the same desc and asc index query on mysql5.6, just for my own curiosity. I will update the execution result of query & performance on another post.
For reference I am going to follow the official link↓ 
https://dev.mysql.com/doc/refman/5.6/en/osx-installation-pkg.html

Thanks for reading till the end. Hoping for some positive comments & please correct me if anything wrong i followed.
Hopefully I will put part2 also soon!