1. 数据库结构

2. insert 测试

insert 的测试包括

1) 批量拼接values()插入

2) 有事务for循环插入

3) 无事务for循环插入

测试 SQL:

 <!-- 普通 insert -->
<insert id="insert"
parameterType="com.qunar.mybatistask.bean.Post"
keyProperty="id">
<![CDATA[ insert into post (
title,
content,
author,
status,
created
) values (
#{title},
#{content},
#{author},
#{status},
#{created}
) ]]>
</insert> <!-- 拼接values insert -->
<insert id="batchInsert"
parameterType="java.util.List">
<![CDATA[
insert into post (
title,
content,
author,
status,
created
) values
]]>
<foreach collection="list" item="post" separator=",">
(
#{post.title},
#{post.content},
#{post.author},
#{post.status},
#{post.created}
)
</foreach>
</insert>

测试代码:

service

    /**
* 批量拼接VALUES() insert
*
* @param postList
* @return
*/
@Override
@Transactional(propagation = Propagation.REQUIRED)
public int batchInsert(List<Post> postList) {
int singleNum = 1000;
int affectedRows = 0;
for (int i = 0; i < Math.ceil((double)(postList.size() / singleNum)); i++) {
affectedRows += sqlSession.insert("post.batchInsert", postList.subList(i * singleNum, (i + 1) * singleNum));
}
return affectedRows;
} /**
* 事务内循环insert
*
* @param postList
* @return
*/
@Override
@Transactional(propagation = Propagation.REQUIRED)
public int createList(List<Post> postList) {
int affectedRows = 0;
for (Post post : postList) {
affectedRows += sqlSession.insert("post.insert", post);
}
return affectedRows;
}

test case:

    /**
* 批量插入效率测试
*
* Method: batchInsert(List<Post> postList)
*
*/
@Test
public void testBatchInsert() throws Exception {
List<Post> postList = Lists.newArrayList();
for (int i = 0; i < 10000; i++) {
Post post = new Post();
post.setAuthor("test");
post.setContent("test");
post.setCreated(new Date());
post.setTitle("test");
post.setStatus(PostStatus.NORMAL);
postList.add(post);
} // 批量拼接SQL插入
long start = System.nanoTime();
int affectedRows = postService.batchInsert(postList);
double duration = System.nanoTime() - start;
System.out.format("batch: %.2f\n", duration / 1.0e9);
System.out.println("affected rows: " + affectedRows); // 事务内循环插入
start = System.nanoTime();
affectedRows = postService.createList(postList);
duration = System.nanoTime() - start;
System.out.format("transaction: %.2f\n", duration / 1.0e9);
System.out.println("affected rows: " + affectedRows); // 无事务直接循环插入
start = System.nanoTime();
affectedRows = 0;
for (Post post : postList)
affectedRows += postService.create(post);
duration = System.nanoTime() - start;
System.out.format("simple: %.2f\n", duration / 1.0e9);
System.out.println("affected rows: " + affectedRows);
}

结果

batch: 1.44
affected rows: 10000
transaction: 2.87
affected rows: 10000
simple: 77.57
affected rows: 10000

总结:

排行

1) 使用拼接的手段,这种插入其实就是batch,只不过这是手动batch

2) 使用事务循环插入,相对于无事务快很多的原因大概是数据库连接和事务开启的次数

3) 无事务循环插入, 我想应该没人这么写

2. 单表循环查询与拼接in查询测试

SQL

<select id="selectById" parameterType="int" resultType="com.qunar.mybatistask.bean.Post">
<![CDATA[ select
id,
title,
content,
author,
status,
created
from
post
where
id = #{id} ]]>
</select> <!-- 拼接where in条件查询 -->
<select id="selectIn" parameterType="java.util.List" resultType="com.qunar.mybatistask.bean.Post">
<![CDATA[
select
id,
title,
content,
author,
status,
created
from
post
where
id in
]]>
<foreach collection="list" item="id" open="(" close=")" separator=",">
#{id}
</foreach>
</select>

Service

    @Override
public Post selectById(int id) {
return sqlSession.selectOne("post.selectById", id);
} @Override
public List<Post> selectByIds(List<Integer> ids) {
List<Post> postList = Lists.newArrayList();
int singleNum = 1000;
int start;
int end;
for (int i = 0; i < Math.ceil(((double)ids.size() / (double)singleNum)); i++) {
start = i * singleNum;
end = (i + 1) * singleNum;
end = end > ids.size() ? ids.size() : end;
List<Post> result = sqlSession.selectList("post.selectIn", ids.subList(start, end));
postList.addAll(result);
}
return postList;
}

test case

    /**
* 使用IN查询效率测试
*
* @throws Exception
*/
@Test
public void testInSelect() throws Exception {
List<Integer> ids = Lists.newArrayList();
for (int i = 1; i < 10000; i++) {
ids.add(i);
} // in 查询
long start = System.nanoTime();
List<Post> list = postService.selectByIds(ids);
double duration = System.nanoTime() - start;
System.out.format("in select: %.2f\n", duration / 1.0e9);
System.out.println("list size: " + list.size()); // 循环查询
list = Lists.newArrayList();
start = System.nanoTime();
for (int id : ids)
list.add(postService.selectById(id));
duration = System.nanoTime() - start;
System.out.format("simple select: %.2f\n", duration / 1.0e9);
System.out.println("list size: " + list.size());
}

结果

in select: 0.55
list size: 9999
simple select: 6.24
list size: 9999

总结:

我想应该没人会用for循环去做查询吧

3. 多表联结查询, join, form 2个table, in, exists 比较

SQL

    <!-- 用于循环查询 -->
<select id="selectAll" resultType="com.qunar.mybatistask.bean.Comment">
<![CDATA[
select
cmt.id as id,
cmt.post_id as postId,
cmt.content as content
from
cmt
]]>
</select> <!-- join 查询 -->
<select id="selectJoin" resultType="com.qunar.mybatistask.bean.Comment">
<![CDATA[
select
cmt.id as id,
cmt.post_id as postId,
cmt.content as content
from
cmt
join
post
on
post.id = cmt.post_id
]]>
</select> <!-- from 2个table -->
<select id="selectTowTable" resultType="com.qunar.mybatistask.bean.Comment">
<![CDATA[
select
cmt.id as id,
cmt.post_id as postId,
cmt.content as content
from
cmt, post
where cmt.post_id = post.id
]]>
</select> <!-- in 联表查询 -->
<select id="selectIn" resultType="com.qunar.mybatistask.bean.Comment">
<![CDATA[
select
cmt.id as id,
cmt.post_id as postId,
cmt.content as content
from
cmt
where
cmt.post_id
in
(
select
post.id
from
post
)
]]>
</select> <!-- exists 联表查询 -->
<select id="selectExists" resultType="com.qunar.mybatistask.bean.Comment">
<![CDATA[
select
cmt.id as id,
cmt.post_id as postId,
cmt.content as content
from
cmt
where
exists
(
select
post.id
from
post
where
post.id = cmt.id
)
]]>
</select>

service

    @Override
public List<Comment> selectTwoTable() {
return sqlSession.selectList("comment.selectTowTable");
} @Override
public List<Comment> selectJoin() {
return sqlSession.selectList("comment.selectJoin");
} @Override
public List<Comment> selectIn() {
return sqlSession.selectList("comment.selectIn");
} @Override
public List<Comment> selectExists() {
return sqlSession.selectList("comment.selectExists");
} @Override
public List<Comment> selectAll() {
return sqlSession.selectList("comment.selectAll");
}

test case

    /**
* 测试JOIN查询效率
*
*/
@Test
public void testJoinSelect() {
// join 查询
long start = System.nanoTime();
List<Comment> list = commentService.selectJoin();
double duration = System.nanoTime() - start;
System.out.format("join select: %.2f\n", duration / 1.0e9);
System.out.println("list size: " + list.size()); // From 两个表查询
start = System.nanoTime();
list = commentService.selectTwoTable();
duration = System.nanoTime() - start;
System.out.format("2 table select: %.2f\n", duration / 1.0e9);
System.out.println("list size: " + list.size()); // in多表查询
start = System.nanoTime();
list = commentService.selectIn();
duration = System.nanoTime() - start;
System.out.format("in multi table select: %.2f\n", duration / 1.0e9);
System.out.println("list size: " + list.size()); // exists多表查询
start = System.nanoTime();
list = commentService.selectExists();
duration = System.nanoTime() - start;
System.out.format("exists multi table select: %.2f\n", duration / 1.0e9);
System.out.println("list size: " + list.size()); // 分次查询, 太慢了, 忽略这种方法的测试吧
// start = System.nanoTime();
// list = commentService.selectAll();
// for (Comment comment : list) {
// postService.selectById(comment.getPostId());
// }
// duration = System.nanoTime() - start;
// System.out.format("separate select: %.2f\n", duration / 1.0e9);
// System.out.println("list size: " + list.size());
}

结果

join select: 2.44
list size: 210000
2 table select: 2.26
list size: 210000
in multi table select: 2.03
list size: 210000
exists multi table select: 2.35
list size: 210000

总结:

21W条数据下效率都差不多,而且我们一般会使用limit去限制查询的条数,所以应该他们的效率差距应该很小,我通过观察explain发现实际上join和from 2个table的方式的查询的执行计划是一模一样的,而in和exists的执行计划也是一模一样的

这里的表结构相对简单,也基本能用上索引 post_id 和 post.id 这些primary, 具体更加复杂的情况也许会影响这几种查询方式的执行计划, 才会体现出他们直接的差距, 当然我也相信他们执行的效率很大程度上是决定于mysql的优化器的优化策略,而这个优化策略很难人为的去判断,所以也不好说

MyBatis+Spring SQL效率测试报告的更多相关文章

  1. Spring Boot 集成 MyBatis和 SQL Server实践

    概 述 Spring Boot工程集成 MyBatis来实现 MySQL访问的示例我们见过很多,而最近用到了微软的 SQL Server数据库,于是本文则给出一个完整的 Spring Boot + M ...

  2. 【spring boot】【mybatis】spring boot中mybatis打印sql语句

    spring boot中mybatis打印sql语句,怎么打印出来?[参考:https://www.cnblogs.com/sxdcgaq8080/p/9100178.html] 在applicati ...

  3. 【记录】spring/springboot 配置mybatis打印sql

    ======================springboot mybatis 打印sql========================================== 方式 一: ##### ...

  4. 集成框架 javaweb开发平台ssmy_m(生成代码) java struts2 mybatis spring maven jquery

    网页地址 http://blog.csdn.net/lpy3654321/article/details/31841573 项目设想,在项目开发中,我们的开发者大多数时间都在反复开发 相同的keywo ...

  5. MyBatis学习(一)、MyBatis简介与配置MyBatis+Spring+MySql

    一.MyBatis简介与配置MyBatis+Spring+MySql 1.1MyBatis简介 MyBatis 是一个可以自定义SQL.存储过程和高级映射的持久层框架.MyBatis 摒除了大部分的J ...

  6. MyBatis详解 与配置MyBatis+Spring+MySql

    MyBatis 是一个可以自定义SQL.存储过程和高级映射的持久层框架.MyBatis 摒除了大部分的JDBC代码.手工设置参数和结果集重获.MyBatis 只使用简单的XML 和注解来配置和映射基本 ...

  7. Maven+druid+MyBatis+Spring+Oracle+Dubbo开发环境搭建

    1.开发工具使用: MyEclipse或Eclipse,数据库使用Oracle.需要用到的软件有Zookeeper(注册中心),Tomcat(Web容器)和Maven(包管理). 2.初始环境配置: ...

  8. mybatis 打印sql 语句

    拦截器 package com.cares.asis.mybatis.interceptor; import java.text.DateFormat; import java.util.Date; ...

  9. 一、MyBatis简介与配置MyBatis+Spring+MySql

    //备注:该博客引自:http://limingnihao.iteye.com/blog/106076 1.1MyBatis简介 MyBatis 是一个可以自定义SQL.存储过程和高级映射的持久层框架 ...

随机推荐

  1. html中<b>标签和<Strong>标签的区别

    关于html标签中b和strong两个的区别,我也是今早上才注意的,以前都是混着用的,早上看书的时候才注意到这两个标签的区别. 用在网页上,默认情况下它们起的均是加粗字体的作用,二者所不同的是,< ...

  2. Python全栈开发之目录

    基础篇 Python全栈开发之1.输入输出与流程控制 Python全栈开发之2.运算符与基本数据结构 Python全栈开发之3.数据类型set补充.深浅拷贝与函数 Python全栈开发之4.内置函数. ...

  3. 【基础知识】JavaScript基础

    [学习日记]JavaScript基础 1,一般写在<head></head>中(其实可以放到任意位置); 2,弹出对话框 <scripttype="text/j ...

  4. 1013 Battle Over Cities (25)(25 point(s))

    problem It is vitally important to have all the cities connected by highways in a war. If a city is ...

  5. 深入理解ajax系列第三篇

    前面的话 我们接收到的响应主体类型可以是多种形式的,包括字符串String.ArrayBuffer对象.二进制Blob对象.JSON对象.javascirpt文件及表示XML文档的Document对象 ...

  6. BZOJ 2726: [SDOI2012]任务安排 [斜率优化DP 二分 提前计算代价]

    2726: [SDOI2012]任务安排 Time Limit: 10 Sec  Memory Limit: 128 MBSubmit: 868  Solved: 236[Submit][Status ...

  7. 数据准备<4>:变量筛选-理论篇

    在上一篇文章<数据准备<3>:数据预处理>中,我们提到降维主要包括两种方式:基于特征选择的降维和基于维度转换的降维,其中基于特征选择的降维通俗的讲就是特征筛选或者变量筛选,是指 ...

  8. UVALive 5968

    假如出现SS 那么表示Spring,如果出现SX的话,就表示WINTER,末尾出现S不管 #include <map> #include <set> #include < ...

  9. PHP运行时强制显示出错信息

    调试很重要 error_reporting(E_ALL); ini_set('display_errors', '1'); 将出错信息输出到一个文本文件 ini_set('error_log', di ...

  10. PCI DSS合规建设ASV扫描介绍

    最近查一些Nessus.Nexpose漏洞扫描工具相关资料,工具介绍都会提到一些审计功能,其中最常见的就是PCI DSS合规性审计.从网上找到一篇介绍较详尽的文章,与大家分享. 原文摘自:http:/ ...