Detailed explanation of cache examples in mybatis

This article mainly introduces the query cache of the mybatis tutorial (first-level cache, second-level cache and integrated ehcache), which has certain reference value. Interested friends can refer to it

1 The meaning of cache

Put the data frequently queried by users in the cache (memory). Users do not need to query the data from the disk (relational database data file), but from the cache query, thereby improving query efficiency and solving the performance problem of high-concurrency systems.

2 mybatis persistence layer cache

mybatis provides first-level cache and second-level cache

Mybatis first-level cache is a SqlSession level. sqlsession can only access the data of its own first-level cache. The second-level cache is across sqlSession and is a mapper-level cache. For The mapper level cache can be shared by different sqlsession.

3 Level 1 cache

3.1 Principle

The first time a query sql is issued, the sql query results are written into the first-level cache of sqlsession. The data structure used in the cache is a map

key: hashcode+ sql+sql input parameter + output parameter (the unique identifier of sql)

value: user information

If the same sqlsession issues the same sql again, it will be fetched from the cache Don't use the database. If there is a commit operation (modify, add, delete) between two times, all the first-level cache area in this sqlsession will be cleared, and the next time you go to the cache to query it, you will not be able to query it, so you have to query it from the database, query it from the database to the cache again.

Every query is first queried from the cache:

If the query is found in the cache, the cache dataReturn directly.

If the query cannot be found in the cache, query it from the database:

3.2 Level 1 cache configuration

Mybatis supports first-level cache by default and does not require configuration.

Note: Mapper agent development is carried out after the integration of mybatis and spring. First-level cache is not supported. Mybatis and spring are integrated. Spring generates the mapper agent according to the mapper template. Object, template Close the sqlsession uniformly at the end.

3.3 Level 1 cache test

//一级缓存 
  @Test 
  public void testCache1() throws Exception { 
 
    SqlSession sqlSession = sqlSessionFactory.openSession(); 
    UserMapper userMapper = sqlSession.getMapper(UserMapper.class); 
     
    //第一次查询用户id为1的用户 
    User user = userMapper.findUserById(1); 
    System.out.println(user); 
     
    //中间修改用户要清空缓存，目的防止查询出脏数据 
    /*user.setUsername("测试用户2"); 
    userMapper.updateUser(user); 
    sqlSession.commit();*/ 
     
    //第二次查询用户id为1的用户 
    User user2 = userMapper.findUserById(1); 
    System.out.println(user2); 
     
    sqlSession.close(); 
     
 
  }

4 Level 2 cache

4.1 Principle

The scope of the second-level cache is the mapper level (the mapper is named with the same Space), mapper creates a cache data structure in namespace units, and the structure is map.

Every time you query, first check whether the second-level cache is enabled. If it is enabled to fetch cached data from the data structure of the second-level cache,

If it is not obtained from the second-level cache, search it from the first-level cache. If it is not found in the first-level cache, query it from the database.

4.2 mybatis second-level cache configuration

Add ## to the core configuration file
SqlMapConfig.xml

#

<setting name="cacheEnabled" value="true"/>

<select id="findOrderListResultMap" resultMap="ordersUserMap" useCache="false">

//二级缓存的测试 
  @Test 
  public void testCache2() throws Exception { 
 
    SqlSession sqlSession1 = sqlSessionFactory.openSession(); 
    SqlSession sqlSession2 = sqlSessionFactory.openSession(); 
    SqlSession sqlSession3 = sqlSessionFactory.openSession(); 
    UserMapper userMapper1 = sqlSession1.getMapper(UserMapper.class); 
    UserMapper userMapper2 = sqlSession2.getMapper(UserMapper.class); 
    UserMapper userMapper3 = sqlSession3.getMapper(UserMapper.class); 
     
    //第一次查询用户id为1的用户 
    User user = userMapper1.findUserById(1); 
    System.out.println(user); 
    sqlSession1.close(); 
     
    //中间修改用户要清空缓存，目的防止查询出脏数据 
    /*user.setUsername("测试用户2"); 
    userMapper3.updateUser(user); 
    sqlSession3.commit(); 
    sqlSession3.close();*/ 
     
     
    //第二次查询用户id为1的用户 
    User user2 = userMapper2.findUserById(1); 
    System.out.println(user2); 
     
    sqlSession2.close(); 
     
 
  }

<cache eviction="FIFO" flushInterval="60000" size="512" readOnly="true"/>

<ehcache xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
  xsi:noNamespaceSchemaLocation="../config/ehcache.xsd"> 
  <!--diskStore：缓存数据持久化的目录 地址 --> 
  <diskStore path="F:\develop\ehcache" /> 
  <defaultCache  
    maxElementsInMemory="1000"  
    maxElementsOnDisk="10000000" 
    eternal="false"  
    overflowToDisk="false"  
    diskPersistent="true" 
    timeToIdleSeconds="120" 
    timeToLiveSeconds="120"  
    diskExpiryThreadIntervalSeconds="120" 
    memoryStoreEvictionPolicy="LRU"> 
  </defaultCache> 
</ehcache>

<!-- 开启二级缓存 --> 
  <!-- 单位：毫秒 --> 
  <cache type="org.mybatis.caches.ehcache.EhcacheCache"> 
    <property name="timeToIdleSeconds" value="12000"/> 
    <property name="timeToLiveSeconds" value="3600"/> 
    <!-- 同ehcache参数maxElementsInMemory --> 
    <property name="maxEntriesLocalHeap" value="1000"/> 
    <!-- 同ehcache参数maxElementsOnDisk --> 
    <property name="maxEntriesLocalDisk" value="10000000"/> 
    <property name="memoryStoreEvictionPolicy" value="LRU"/> 
  </cache>