Leaf block contention in InnoDB tables can significantly impact the performance of your MySQL database, especially under high concurrency. This situation typically occurs when multiple transactions are trying to modify or lock rows in the same leaf blocks of an index, leading to a bottleneck. Here are several tips and tricks to reduce leaf block contention:

1. Increase innodb_page_size

• Consider increasing the innodb_page_size configuration. The default page size is 16KB, but if your workload involves large rows or if you're experiencing high contention, increasing the page size can reduce the number of row locks within the same leaf block. However, be cautious as this change requires recreating the database and can affect disk usage and memory utilization.

2. Partitioning

• Implement table partitioning. By partitioning a table, you're essentially dividing it into smaller, more manageable pieces based on a key. This can help distribute the row locks across multiple parts of the table, reducing contention on any single leaf block.

3. Use Covering Indexes

• Utilize covering indexes effectively. A covering index includes all the fields required by a query, which can significantly reduce the need to access the actual table rows for data, thereby minimizing contention on leaf blocks of the primary data.

4. Optimize Queries

• Optimize your queries to minimize locking. This includes using proper indexes to ensure that queries are as efficient as possible, thus reducing the time locks are held.

• Use the LOW_PRIORITY write operations for less critical updates to decrease their priority and reduce contention.

5. Adjust innodb_autoinc_lock_mode

• If you're using auto-increment columns, consider adjusting innodb_autoinc_lock_mode. Setting it to 2(interleaved) mode reduces contention on auto-increment locks by allowing statements to get the next auto-increment value without waiting for other statements to complete, suitable for high concurrency INSERT operations.

6. Fine-tune Transaction Isolation Levels

• Adjust the transaction isolation level. Lowering the isolation level can reduce locking overhead. For instance, using READ COMMITTED instead of REPEATABLE READ can decrease the number of locks set by a transaction, reducing contention. However, ensure that this change is compatible with your application's consistency requirements.

7. Batching Inserts and Updates

• Batch inserts and updates when possible. Batching reduces the number of times locks are acquired and released, decreasing the potential for contention.

8. Monitoring and Analyzing Contention

• Monitor your database performance closely. Tools like SHOW ENGINE INNODB STATUS and performance schema tables can help identify contention points.

• Use INFORMATION_SCHEMA.INNODB_TRX and INNODB_LOCKS tables to analyze locking behavior and identify contentious queries.

9. Row Format and Compression

• Consider changing the row format. Formats like DYNAMIC and COMPRESSED can store more data on a page, reducing the need for accessing multiple leaf blocks for queries. This change, however, should be tested as it might have implications on CPU usage due to compression.

10. Application-Level Optimizations

• On the application side, minimize transaction sizes and durations to lessen the time locks are held. Also, consider logical partitioning at the application level, spreading write operations across different tables or databases to reduce contention.

Reducing leaf block contention in InnoDB requires a combination of database configuration adjustments, query optimization, and strategic schema design. By implementing these tips and continuously monitoring your database's performance, you can significantly mitigate the impact of contention on your database's throughput and response times.