【转载】hibernate缓存机制

一级缓存(session级别)java


咱们来看看hibernate提供的一级缓存sql

//此时会发出一条sql,将全部学生所有查询出来,并放到session的一级缓存当中。当再次查询学生信息时,会首先去缓存中看是否存在,若是不存在,再去数据库中查询。这就是hibernate的一级缓存(session缓存)
List<Student> stus = (List<Student>)session.createQuery("from Student") .setFirstResult(0).setMaxResults(30).list();
Student stu = (Student)session.load(Student.class, 1)

咱们来看看控制台输出数据库

Hibernate: select student0_.id as id2_, student0_.name as name2_, student0_.rid as rid2_, student0_.sex as sex2_ from t_student student0_ limit ?

咱们看到此时hibernate仅仅只会发出一条 sql 语句,由于第一行代码就会将整个的对象查询出来,放到session的一级缓存中去,当我若是须要再次查询学生对象时,此时首先会去缓存中看是否存在该对象,若是存在,则直接从缓存中取出,就不会再发sql了,可是要注意一点:hibernate的一级缓存是session级别的,因此若是session关闭后,缓存就没了,此时就会再次发sql去查数据库缓存

    try
        {
            session = HibernateUtil.openSession();
            
            /**
             * 此时会发出一条sql,将全部学生所有查询出来,并放到session的一级缓存当中
             * 当再次查询学生信息时,会首先去缓存中看是否存在,若是不存在,再去数据库中查询
             * 这就是hibernate的一级缓存(session缓存)
             */
            List<Student> stus = (List<Student>)session.createQuery("from Student")
                                    .setFirstResult(0).setMaxResults(30).list();
            Student stu = (Student)session.load(Student.class, 1);
            System.out.println(stu.getName() + "-----------");
        }
        catch (Exception e)
        {
            e.printStackTrace();
        }
        finally
        {
            HibernateUtil.close(session);
        }
        /**
         * 当session关闭之后,session的一级缓存也就没有了,这时就又会去数据库中查询
         */
        session = HibernateUtil.openSession();
        Student stu = (Student)session.load(Student.class, 1);
        System.out.println(stu.getName() + "-----------");
Hibernate: select student0_.id as id2_, student0_.name as name2_, student0_.sex as sex2_, student0_.rid as rid2_ from t_student student0_ limit ?

Hibernate: 
select student0_.id as id2_2_, student0_.name as name2_2_, student0_.sex as sex2_2_, student0_.rid as rid2_2_,
classroom1_.id as id1_0_, classroom1_.name as name1_0_, classroom1_.sid as sid1_0_, special2_.id as id0_1_, special2_.name as name0_1_, special2_.type as type0_1_
from t_student student0_ left outer join t_classroom classroom1_ on student0_.rid
=classroom1_.id left outer join t_special special2_ on classroom1_.sid=special2_.id where student0_.id=?

咱们看到此时会发出两条sql语句,由于session关闭之后,一级缓存就不存在了,因此若是再查询的时候,就会再发sql。要解决这种问题,咱们应该怎么作呢?这就要咱们来配置hibernate的二级缓存了,也就是sessionFactory级别的缓存。session

 

二级缓存(sessionFactory级别)app


使用hibernate二级缓存,咱们首先须要对其进行配置,配置步骤以下:ide

1.hibernate并无提供相应的二级缓存的组件,因此须要加入额外的二级缓存包,经常使用的二级缓存包是EHcache。这个咱们在下载好的hibernate的lib->optional->ehcache下能够找到(我这里使用的hibernate4.1.7版本),而后将里面的几个jar包导入便可。性能

2.在hibernate.cfg.xml配置文件中配置咱们二级缓存的一些属性:测试

<!-- 开启二级缓存 --> <property name="hibernate.cache.use_second_level_cache">true</property> <!-- 二级缓存的提供类 在hibernate4.0版本之后咱们都是配置这个属性来指定二级缓存的提供类--> <property name="hibernate.cache.region.factory_class">org.hibernate.cache.ehcache.EhCacheRegionFactory</property> <!-- 二级缓存配置文件的位置 --> <property name="hibernate.cache.provider_configuration_file_resource_path">ehcache.xml</property>

我这里使用的是hibernate4.1.7版本,若是是使用hibernate3的版本的话,那么二级缓存的提供类则要配置成这个:fetch

<!--这个类在4.0版本之后已经不建议被使用了-->
<property name="hibernate.cache.provider_class">net.sf.ehcache.hibernate.EhCacheProvider</property>

3.配置hibernate的二级缓存是经过使用 ehcache的缓存包,因此咱们须要建立一个 ehcache.xml 的配置文件,来配置咱们的缓存信息,将其放到项目根目录下

<ehcache>

    <!-- Sets the path to the directory where cache .data files are created.

         If the path is a Java System Property it is replaced by
         its value in the running VM.

         The following properties are translated:
         user.home - User's home directory
         user.dir - User's current working directory
         java.io.tmpdir - Default temp file path -->
  
  <!--指定二级缓存存放在磁盘上的位置-->
    <diskStore path="user.dir"/>  

  <!--咱们能够给每一个实体类指定一个对应的缓存,若是没有匹配到该类,则使用这个默认的缓存配置-->
    <defaultCache
        maxElementsInMemory="10000"  //在内存中存放的最大对象数
        eternal="false"         //是否永久保存缓存,设置成false
        timeToIdleSeconds="120"    
        timeToLiveSeconds="120"    
        overflowToDisk="true"     //若是对象数量超过内存中最大的数,是否将其保存到磁盘中,设置成true
        />
  
  <!--

    一、timeToLiveSeconds的定义是:以建立时间为基准开始计算的超时时长;
    二、timeToIdleSeconds的定义是:在建立时间和最近访问时间中取出离如今最近的时间做为基准计算的超时时长;
    三、若是仅设置了timeToLiveSeconds,则该对象的超时时间=建立时间+timeToLiveSeconds,假设为A;
    四、若是没设置timeToLiveSeconds,则该对象的超时时间=max(建立时间,最近访问时间)+timeToIdleSeconds,假设为B;
    五、若是二者都设置了,则取出A、B最少的值,即min(A,B),表示只要有一个超时成当即算超时。

  -->

  <!--能够给每一个实体类指定一个配置文件,经过name属性指定,要使用类的全名-->
    <cache name="com.xiaoluo.bean.Student"
        maxElementsInMemory="10000"
        eternal="false"
        timeToIdleSeconds="300"
        timeToLiveSeconds="600"
        overflowToDisk="true"
        />

    <cache name="sampleCache2"
        maxElementsInMemory="1000"
        eternal="true"
        timeToIdleSeconds="0"
        timeToLiveSeconds="0"
        overflowToDisk="false"
        /> -->


</ehcache>

4.开启咱们的二级缓存

①若是使用xml配置,咱们须要在 Student.hbm.xml 中加上一下配置:

<hibernate-mapping package="com.xiaoluo.bean">
    <class name="Student" table="t_student">
        <!-- 二级缓存通常设置为只读的 -->
        <cache usage="read-only"/>
        <id name="id" type="int" column="id">
            <generator class="native"/>
        </id>
        <property name="name" column="name" type="string"></property>
        <property name="sex" column="sex" type="string"></property>
        <many-to-one name="room" column="rid" fetch="join"></many-to-one>
    </class>
</hibernate-mapping>

二级缓存的使用策略通常有这几种:read-only、nonstrict-read-write、read-write、transactional。

注意:咱们一般使用二级缓存都是将其配置成 read-only ,即咱们应当在那些不须要进行修改的实体类上使用二级缓存,不然若是对缓存进行读写的话,性能会变差,这样设置缓存就失去了意义。

②若是使用annotation配置,咱们须要在Student这个类上加上这样一个注解:

@Entity
@Table(name="t_student")
@Cache(usage=CacheConcurrencyStrategy.READ_ONLY)  //  表示开启二级缓存,并使用read-only策略
public class Student
{
    private int id;
    private String name;
    private String sex;
    private Classroom room;
    .......
}

这样咱们的二级缓存配置就算完成了,接下来咱们来经过测试用例测试下咱们的二级缓存是否起做用

①二级缓存是sessionFactory级别的缓存

TestCase1:

public class TestSecondCache
{
    @Test
    public void testCache1()
    {
        Session session = null;
        try
        {
            session = HibernateUtil.openSession();

            Student stu = (Student) session.load(Student.class, 1);
            System.out.println(stu.getName() + "-----------");
        }
        catch (Exception e)
        {
            e.printStackTrace();
        }
        finally
        {
            HibernateUtil.close(session);
        }
        try
        {
            /**
             * 即便当session关闭之后,由于配置了二级缓存,而二级缓存是sessionFactory级别的,因此会从缓存中取出该数据
             * 只会发出一条sql语句
             */
            session = HibernateUtil.openSession();
            Student stu = (Student) session.load(Student.class, 1);
            System.out.println(stu.getName() + "-----------");
            /**
             * 由于设置了二级缓存为read-only,因此不能对其进行修改
             */
            session.beginTransaction();
            stu.setName("aaa");
            session.getTransaction().commit();
        }
        catch (Exception e)
        {
            e.printStackTrace();
            session.getTransaction().rollback();
        }
        finally
        {
            HibernateUtil.close(session);
        }
    }

 

Hibernate: 
      select student0_.id as id2_2_, student0_.name as name2_2_, student0_.sex as sex2_2_, student0_.rid as rid2_2_,
      classroom1_.id as id1_0_, classroom1_.name as name1_0_, classroom1_.sid as sid1_0_,
      special2_.id as id0_1_, special2_.name as name0_1_, special2_.type as type0_1_
      from t_student student0_ left outer join t_classroom classroom1_ on student0_.rid=classroom1_.id left outer join t_special special2_ on classroom1_.sid=special2_.id where student0_.id=? aaa----------- aaa-----------

由于二级缓存是sessionFactory级别的缓存,咱们看到,在配置了二级缓存之后,当咱们session关闭之后,咱们再去查询对象的时候,此时hibernate首先会去二级缓存中查询是否有该对象,有就不会再发sql了。

②二级缓存缓存的仅仅是对象,若是查询出来的是对象的一些属性,则不会被加到缓存中去

TestCase2:

   @Test
    public void testCache2()
    {
        Session session = null;
        try
        {
            session = HibernateUtil.openSession();
        //注意:二级缓存中缓存的仅仅是对象,而下面这里只保存了姓名和性别两个字段,因此 不会被加载到二级缓存里面
List<Object[]> ls = (List<Object[]>) session.createQuery("select stu.name, stu.sex from Student stu").setFirstResult(0).setMaxResults(30).list(); } catch (Exception e) { e.printStackTrace(); } finally { HibernateUtil.close(session); } try { //因为二级缓存缓存的是对象,因此此时会发出两条sql session = HibernateUtil.openSession(); Student stu = (Student) session.load(Student.class, 1); System.out.println(stu); } catch (Exception e) { e.printStackTrace(); } }
Hibernate: select student0_.name as col_0_0_, student0_.sex as col_1_0_ from t_student student0_ limit ?
Hibernate: select  student0_.id as id2_2_, student0_.name as name2_2_, student0_.sex as sex2_2_, student0_.rid as rid2_2_, 
            classroom1_.id as id1_0_, classroom1_.name as name1_0_, classroom1_.sid as sid1_0_,
            special2_.id as id0_1_, special2_.name as name0_1_, special2_.type as type0_1_
       from t_student student0_ left outer join t_classroom classroom1_ on student0_.rid
=classroom1_.id left outer join t_special special2_ on classroom1_.sid=special2_.id where student0_.id=?

咱们看到这个测试用例,若是咱们只是取出对象的一些属性的话,则不会将其保存到二级缓存中去,由于二级缓存缓存的仅仅是对象

④二级缓存会缓存 hql 语句吗?

TestCase4:

  @Test
    public void testCache4()
    {
        Session session = null;
        try
        {
            session = HibernateUtil.openSession();
            List<Student> ls = session.createQuery("from Student").setFirstResult(0).setMaxResults(50).list();
        }
        catch (Exception e)
        {
            e.printStackTrace();
        }
        finally
        {
            HibernateUtil.close(session);
        }
        try
        {
            //使用List会发出两条如出一辙的sql,此时若是但愿不发sql就须要使用查询缓存
            session = HibernateUtil.openSession();
            List<Student> ls = session.createQuery("from Student").setFirstResult(0).setMaxResults(50).list();
            Iterator<Student> stu = ls.iterator();
            for(;stu.hasNext();)
            {
                Student student = stu.next();
                System.out.println(student.getName());
            }
        }
        catch (Exception e)
        {
            e.printStackTrace();
        }
        finally
        {
            HibernateUtil.close(session);
        }
    }
Hibernate: select student0_.id as id2_, student0_.name as name2_, student0_.sex as sex2_, student0_.rid as rid2_ from t_student student0_ limit ?
Hibernate: select student0_.id as id2_, student0_.name as name2_, student0_.sex as sex2_, student0_.rid as rid2_ from t_student student0_ limit ?

咱们看到,当咱们若是经过 list() 去查询两次对象时,二级缓存虽然会缓存查询出来的对象,可是咱们看到发出了两条相同的查询语句,这是由于二级缓存不会缓存咱们的hql查询语句,要想解决这个问题,咱们就要配置咱们的查询缓存了。

 

查询缓存(sessionFactory级别)


咱们若是要配置查询缓存,只须要在hibernate.cfg.xml中加入一条配置便可:

<!-- 开启查询缓存 --> <property name="hibernate.cache.use_query_cache">true</property>

而后咱们若是在查询hql语句时要使用查询缓存,就须要在查询语句后面设置这样一个方法:

List<Student> ls = session.createQuery("from Student where name like ?")
                    .setCacheable(true)  //开启查询缓存,查询缓存也是SessionFactory级别的缓存 .setParameter(0, "%王%") .setFirstResult(0).setMaxResults(50).list();

若是是在annotation中,咱们还须要在这个类上加上这样一个注解:@Cacheable

测试案例

①查询缓存也是sessionFactory级别的缓存

TestCase1:

@Test
    public void test2() {
        Session session = null;
        try {
            /**
             * 此时会发出一条sql取出全部的学生信息
             */
            session = HibernateUtil.openSession();
            List<Student> ls = session.createQuery("from Student")
                    .setCacheable(true)  //开启查询缓存,查询缓存也是sessionFactory级别的缓存
                    .setFirstResult(0).setMaxResults(50).list();
            Iterator<Student> stus = ls.iterator();
            for(;stus.hasNext();) {
                Student stu = stus.next();
                System.out.println(stu.getName());
            }
        } catch (Exception e) {
            e.printStackTrace();
        } finally {
            HibernateUtil.close(session);
        }
        try {
            /**
             * 此时会发出一条sql取出全部的学生信息
             */
            session = HibernateUtil.openSession();
            List<Student> ls = session.createQuery("from Student")
                    .setCacheable(true)  //开启查询缓存,查询缓存也是sessionFactory级别的缓存
                    .setFirstResult(0).setMaxResults(50).list();
            Iterator<Student> stus = ls.iterator();
            for(;stus.hasNext();) {
                Student stu = stus.next();
                System.out.println(stu.getName());
            }
        } catch (Exception e) {
            e.printStackTrace();
        } finally {
            HibernateUtil.close(session);
        }
    }


Hibernate: select student0_.id as id2_, student0_.name as name2_, student0_.sex as sex2_, student0_.rid as rid2_ from t_student student0_ limit ?

咱们看到,此时若是咱们发出两条相同的语句,hibernate也只会发出一条sql,由于已经开启了查询缓存了,而且查询缓存也是sessionFactory级别的

②只有当 HQL 查询语句彻底相同时,连参数设置都要相同,此时查询缓存才有效

TestCase2:

  @Test
    public void test3() {
        Session session = null;
        try {
            /**
             * 此时会发出一条sql取出全部的学生信息
             */
            session = HibernateUtil.openSession();
            List<Student> ls = session.createQuery("from Student where name like ?")
                    .setCacheable(true)//开启查询缓存,查询缓存也是SessionFactory级别的缓存
                    .setParameter(0, "%王%")
                    .setFirstResult(0).setMaxResults(50).list();
            Iterator<Student> stus = ls.iterator();
            for(;stus.hasNext();) {
                Student stu = stus.next();
                System.out.println(stu.getName());
            }
        } catch (Exception e) {
            e.printStackTrace();
        } finally {
            HibernateUtil.close(session);
        }
        session = null;
        try {
            /**
             * 此时会发出一条sql取出全部的学生信息
             */
            session = HibernateUtil.openSession();
            /**
             * 只有当HQL彻底相同的时候,连参数都要相同,查询缓存才有效
             */
//            List<Student> ls = session.createQuery("from Student where name like ?")
//                    .setCacheable(true)//开启查询缓存,查询缓存也是SessionFactory级别的缓存
//                    .setParameter(0, "%王%")
//                    .setFirstResult(0).setMaxResults(50).list();
            List<Student> ls = session.createQuery("from Student where name like ?")
                    .setCacheable(true)//开启查询缓存,查询缓存也是SessionFactory级别的缓存
                    .setParameter(0, "%张%")
                    .setFirstResult(0).setMaxResults(50).list();
            Iterator<Student> stus = ls.iterator();
            for(;stus.hasNext();) {
                Student stu = stus.next();
                System.out.println(stu.getName());
            }
        } catch (Exception e) {
            e.printStackTrace();
        } finally {
            HibernateUtil.close(session);
        }
    }


Hibernate: select student0_.id as id2_, student0_.name as name2_, student0_.sex as sex2_, student0_.rid as rid2_ from t_student student0_ where student0_.name like ? limit ?

Hibernate: select student0_.id as id2_, student0_.name as name2_, student0_.sex as sex2_, student0_.rid as rid2_ from t_student student0_ where student0_.name like ? limit ?

咱们看到,若是咱们的hql查询语句不一样的话,咱们的查询缓存也没有做用

③首先先将 Student 对象上的二级缓存先注释掉:

<!-- 二级缓存通常设置为只读的 -->
<!--  <cache usage="read-only"/>  -->

TestCase4:
复制代码

  @Test
    public void test4() {
        Session session = null;
        try {
           
        //查询缓存缓存的不是对象而是id
            session = HibernateUtil.openSession();
            List<Student> ls = session.createQuery("from Student where name like ?")
                    .setCacheable(true)//开启查询缓存,查询缓存也是SessionFactory级别的缓存
                    .setParameter(0, "%王%")
                    .setFirstResult(0).setMaxResults(50).list();
            Iterator<Student> stus = ls.iterator();
            for(;stus.hasNext();) {
                Student stu = stus.next();
                System.out.println(stu.getName());
            }
        } catch (Exception e) {
            e.printStackTrace();
        } finally {
            HibernateUtil.close(session);
        }
        
        session = null;
        try {
            /**
             * 查询缓存缓存的是id,此时因为在缓存中已经存在了这样的一组学生数据,可是仅仅只是缓存了
             * id,因此此处会发出大量的sql语句根据id取对象,因此若是使用查询缓存必须开启二级缓存
             */
            session = HibernateUtil.openSession();
            List<Student> ls = session.createQuery("from Student where name like ?")
                    .setCacheable(true)//开启查询缓存,查询缓存也是SessionFactory级别的缓存
                    .setParameter(0, "%王%")
                    .setFirstResult(0).setMaxResults(50).list();
            Iterator<Student> stus = ls.iterator();
            for(;stus.hasNext();) {
                Student stu = stus.next();
                System.out.println(stu.getName());
            }
        } catch (Exception e) {
            e.printStackTrace();
        } finally {
            HibernateUtil.close(session);
        }
    }
Hibernate: select student0_.id as id2_, student0_.name as name2_, student0_.sex as sex2_, student0_.rid as rid2_ from t_student student0_ where student0_.name like ? limit ?

Hibernate: select  student0_.id as id2_2_, student0_.name as name2_2_, student0_.sex as sex2_2_, student0_.rid as rid2_2_, 
            classroom1_.id as id1_0_, classroom1_.name as name1_0_, classroom1_.sid as sid1_0_,
            special2_.id as id0_1_, special2_.name as name0_1_, special2_.type as type0_1_
       from t_student student0_ left outer join t_classroom classroom1_ on student0_.rid
=classroom1_.id left outer join t_special special2_ on classroom1_.sid=special2_.id where student0_.id=?
Hibernate: select  student0_.id as id2_2_, student0_.name as name2_2_, student0_.sex as sex2_2_, student0_.rid as rid2_2_, 
            classroom1_.id as id1_0_, classroom1_.name as name1_0_, classroom1_.sid as sid1_0_,
            special2_.id as id0_1_, special2_.name as name0_1_, special2_.type as type0_1_
       from t_student student0_ left outer join t_classroom classroom1_ on student0_.rid=classroom1_.id left outer join t_special special2_ on classroom1_.sid=special2_.id where student0_.id=?
Hibernate: select  student0_.id as id2_2_, student0_.name as name2_2_, student0_.sex as sex2_2_, student0_.rid as rid2_2_, 
            classroom1_.id as id1_0_, classroom1_.name as name1_0_, classroom1_.sid as sid1_0_,
            special2_.id as id0_1_, special2_.name as name0_1_, special2_.type as type0_1_
       from t_student student0_ left outer join t_classroom classroom1_ on student0_.rid=classroom1_.id left outer join t_special special2_ on classroom1_.sid=special2_.id where student0_.id=?
Hibernate: select  student0_.id as id2_2_, student0_.name as name2_2_, student0_.sex as sex2_2_, student0_.rid as rid2_2_, 
            classroom1_.id as id1_0_, classroom1_.name as name1_0_, classroom1_.sid as sid1_0_,
            special2_.id as id0_1_, special2_.name as name0_1_, special2_.type as type0_1_
       from t_student student0_ left outer join t_classroom classroom1_ on student0_.rid=classroom1_.id left outer join t_special special2_ on classroom1_.sid=special2_.id where student0_.id=?
.........................

咱们看到,当咱们将二级缓存注释掉之后,在使用查询缓存时,也会出现 N+1 的问题,为何呢?

由于查询缓存缓存的也仅仅是对象的id,因此第一条 sql 也是将对象的id都查询出来,可是当咱们后面若是要获得每一个对象的信息的时候,此时又会发sql语句去查询,因此,若是要使用查询缓存,咱们必定也要开启咱们的二级缓存,这样就不会出现 N+1 问题了。(上面这段话好像有点问题,我测试了一下,查询非ID字段,好比select name from student,这样的查询能很好缓存。这个文章 http://yangfei520.blog.51cto.com/1041581/287380 的这段话就解释清楚了hibernate的查询缓存是主要是针对普通属性结果集的缓存, 而对于实体对象的结果集只缓存id。在一级缓存,二级缓存和查询缓存都打开的状况下做查询操做时这样的:查询普通属性,会先到查询缓存中取,若是没有,则查询数据库;查询实体,会先到查询缓存中取id,若是有,则根据id到缓存(一级/二级)中取实体,若是缓存中取不到实体,再查询数据库,此时查就是一个N+1的效果。和一级/二级缓存不一样,查询缓存的生命周期 ,是不肯定的,当前关联的表发生改变时,查询缓存的生命周期结束

相关文章
相关标签/搜索