登录注册

当前位置：首页 > 文章列表 > 数据库 > MySQL > mysql性能分析诊断

mysql性能分析诊断

来源：SegmentFault 2023-02-16 15:30:25 0浏览 收藏

知识点掌握了，还需要不断练习才能熟练运用。下面golang学习网给大家带来一个数据库开发实战，手把手教大家学习《mysql性能分析诊断》，在实现功能的过程中也带大家重新温习相关知识点，温故而知新，回头看看说不定又有不一样的感悟！

网摘sql优化口诀

全值匹配我最爱，最左前缀要遵守 
带头大哥不能死，中间兄弟不能断 
索引列上少计算，范围之后全失效 
LIKE符号写最右，覆盖索引不写星 
不等空值还有or，索引失效要少用 
var引号不能丢，SQL高级也不难 
分组之前必排序，一定要上索引啊

案例:千万级数据使用limit实现分页优化

https://www.jianshu.com/p/c62...
1.使用覆盖索引

CREATE TABLE `user` (
  `id` int(11) unsigned NOT NULL AUTO_INCREMENT,
  `name` varchar(32) NOT NULL DEFAULT '' COMMENT '姓名',
  `age` tinyint(4) NOT NULL COMMENT '年纪',
  `sex` tinyint(4) NOT NULL COMMENT '性别',
  `email` varchar(32) NOT NULL DEFAULT '' COMMENT '邮箱',
  `ctime` int(11) NOT NULL COMMENT '创建时间',
  PRIMARY KEY (`id`),
  KEY `index_email` (`email`(7)),
  KEY `index_id_email` (`id`,`email`)
) ENGINE=InnoDB AUTO_INCREMENT=131604 DEFAULT CHARSET=utf8mb4;
mysql> select SQL_NO_CACHE id,email from user limit 100000,10;
+--------+-------------+
| id | email |
+--------+-------------+
| 100001 | zhsb@qq.com |
| 100002 | zhsb@qq.com |
| 100003 | zhsb@qq.com |
| 100004 | zhsb@qq.com |
| 100005 | zhsb@qq.com |
| 100006 | zhsb@qq.com |
| 100007 | zhsb@qq.com |
| 100008 | zhsb@qq.com |
| 100009 | zhsb@qq.com |
| 100010 | zhsb@qq.com |
+--------+-------------+
10 rows in set, 1 warning (0.02 sec)
 
mysql> select SQL_NO_CACHE id,email,name from user limit 100000,10;
+--------+-------------+-------+
| id | email | name |
+--------+-------------+-------+
| 100001 | zhsb@qq.com | 张xx |
| 100002 | zhsb@qq.com | 张xx |
| 100003 | zhsb@qq.com | 张xx |
| 100004 | zhsb@qq.com | 张xx |
| 100005 | zhsb@qq.com | 张xx |
| 100006 | zhsb@qq.com | 张xx |
| 100007 | zhsb@qq.com | 张xx |
| 100008 | zhsb@qq.com | 张xx |
| 100009 | zhsb@qq.com | 张xx |
| 100010 | zhsb@qq.com | 张xx |
+--------+-------------+-------+
10 rows in set, 1 warning (0.03 sec)
 
mysql> explain select SQL_NO_CACHE id,email from user limit 100000,10;
+----+-------------+-------+------------+-------+---------------+----------------+---------+------+--------+----------+-------------+
| id | select_type | table | partitions | type | possible_keys | key | key_len | ref | rows | filtered | Extra |
+----+-------------+-------+------------+-------+---------------+----------------+---------+------+--------+----------+-------------+
| 1 | SIMPLE | user | NULL | index | NULL | index_id_email | 134 | NULL | 131052 | 100.00 | Using index |
+----+-------------+-------+------------+-------+---------------+----------------+---------+------+--------+----------+-------------+
1 row in set, 2 warnings (0.01 sec)
 
mysql> explain select SQL_NO_CACHE id,email,name from user limit 100000,10;
+----+-------------+-------+------------+------+---------------+------+---------+------+--------+----------+-------+
| id | select_type | table | partitions | type | possible_keys | key | key_len | ref | rows | filtered | Extra |
+----+-------------+-------+------------+------+---------------+------+---------+------+--------+----------+-------+
| 1 | SIMPLE | user | NULL | ALL | NULL | NULL | NULL | NULL | 131052 | 100.00 | NULL |
+----+-------------+-------+------------+------+---------------+------+---------+------+--------+----------+-------+
1 row in set, 2 warnings (0.00 sec)
 
Using index:使用到了覆盖索引
 
mysql> show profiles;
+----------+------------+---------------------------------------------------------------------+
| Query_ID | Duration | Query |
+----------+------------+---------------------------------------------------------------------+
| 204 | 0.00040800 | select SQL_NO_CACHE id,email from user limit 100,10 |
| 205 | 0.00039600 | select SQL_NO_CACHE id,email from user limit 100,10 |
| 206 | 0.00645100 | explain select SQL_NO_CACHE id,email from user limit 100,10 |
| 207 | 0.00036400 | explain select SQL_NO_CACHE email from user limit 100,10 |
| 208 | 0.00053500 | explain select SQL_NO_CACHE id,email,name from user limit 100,10 |
| 209 | 0.00698800 | select SQL_NO_CACHE id,email from user limit 100,10 |
| 210 | 0.00067400 | select SQL_NO_CACHE id,email,name from user limit 100,10 |
| 211 | 0.00045100 | select SQL_NO_CACHE id,email,name from user limit 100,10 |
| 212 | 0.00032900 | select SQL_NO_CACHE id,email from user limit 100,10 |
| 213 | 0.02265800 | select SQL_NO_CACHE id,email from user limit 100000,10 |
| 214 | 0.03214000 | select SQL_NO_CACHE id,email,name from user limit 100000,10 |
| 215 | 0.00046200 | explain select SQL_NO_CACHE id,email from user limit 100000,10 |
| 216 | 0.00040000 | explain select SQL_NO_CACHE id,email,name from user limit 100000,10 |
| 217 | 0.01920500 | select SQL_NO_CACHE id,email from user limit 100000,10 |
| 218 | 0.03084100 | select SQL_NO_CACHE id,email,name from user limit 100000,10 |
+----------+------------+---------------------------------------------------------------------+

观察 query_id是217和218的两条sql,就是刚才执行得出的,时间得到明显提升,且用到了index_id_email索引,使用到覆盖索引，
数据直接从索引中就可以获取到,不需要回表从主键索引里获取数据, 覆盖索引是指，索引上的信息足够满足查询请求，不需要再回到主键索引上去取数据。由于覆盖索引可以减少树的搜索次数，显著提升查询性能，所以使用覆盖索引是一个常用的性能优化手段。
使用SQL_NO_CACHE强制不走mysql查询缓存

2.使用 id>=的形式:

select SQL_NO_CACHE * from user where id>=(select id from user limit 10000, 1) limit 10;

连接（JOIN）.. 之所以更有效率一些，是因为 MySQL不需要在内存中创建临时表来完成这个逻辑上的需要两个步骤的查询工作

mysql> explain select SQL_NO_CACHE * from user where id>=(select id from user limit 10000, 1) limit 10;
+----+-------------+-------+------------+-------+------------------------+-------------+---------+------+--------+----------+-------------+
| id | select_type | table | partitions | type  | possible_keys          | key         | key_len | ref  | rows   | filtered | Extra       |
+----+-------------+-------+------------+-------+------------------------+-------------+---------+------+--------+----------+-------------+
|  1 | PRIMARY     | user  | NULL       | range | PRIMARY,index_id_email | PRIMARY     | 4       | NULL |  65526 |   100.00 | Using where |
|  2 | SUBQUERY    | user  | NULL       | index | NULL                   | index_email | 30      | NULL | 131052 |   100.00 | Using index |
+----+-------------+-------+------------+-------+------------------------+-------------+---------+------+--------+----------+-------------+
2 rows in set, 2 warnings (0.00 sec)

从慢查询日志入手开始搞！！！

1.开启慢查询
mysql> set slow_query_log=1;
ERROR 1229 (HY000): Variable 'slow_query_log' is a GLOBAL variable and should be set with SET GLOBA
开启全局慢查询日志
mysql> set global slow_query_log=1;
Query OK, 0 rows affected (0.00 sec)
查看是否开启慢查询日志
mysql> show variables like "slow_query_log";
+----------------+-------+
| Variable_name  | Value |
+----------------+-------+
| slow_query_log | ON    |
+----------------+-------+
1 row in set (0.00 sec)
查看慢查询入日志文件位置
mysql> show variables like "slow_query_log_file";
+---------------------+--------------------------------------+
| Variable_name       | Value                                |
+---------------------+--------------------------------------+
| slow_query_log_file | /usr/local/var/mysql/itech8-slow.log |
+---------------------+--------------------------------------+
1 row in set (0.01 sec)
查看慢查询日志的时间设置,默认是10s内的查询则为慢查询
 
mysql> show variables like '%long_query_time%';
+-----------------+-----------+
| Variable_name   | Value     |
+-----------------+-----------+
| long_query_time | 10.000000 |
+-----------------+-----------+
1 row in set (0.01 sec)
 
设置查询时间1s内的记录为慢查询日志
mysql> set long_query_time=1;
Query OK, 0 rows affected (0.00 sec)
 
mysql> show variables like '%long_query_time%';
+-----------------+----------+
| Variable_name   | Value    |
+-----------------+----------+
| long_query_time | 1.000000 |
+-----------------+----------+
设置日期过期天数
mysql> set global expire_logs_days=30;
Query OK, 0 rows affected (0.00 sec)

使用mysqldumpslow工具分析慢查询日志

得到返回记录集最多的10个SQL

mysqldumpslow –s r –t 10 /data/logs/mysql/slowquery.log

得到访问次数最多的10个SQL

mysqldumpslow –s c –t 10 /data/logs/mysql/slowquery.log

得到按照时间排序的前10条里面含有左连接的查询

mysqldumpslow –s t –t 10 –g "left join" /data/logs/mysql/slowquery.log

另外建议在使用这些命令时结合|和more使用，否则可能出现爆破情况

mysqldumpslow –s r –t 10 /data/logs/mysql/slowquery.log|more

参数含义
s: 表示按照何种方式排序
c：访问次数
l：锁定时间
r：返回记录
t：查询时间
al：平均锁定时间
t：返回前面多少条的数据
g：后面搭配一个正则表达式

root@iZ257v6fpmnZ ~]# mysqldumpslow -s -r -t 2 /data/logs/mysql/slowquery.log
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_CTYPE = "UTF-8",
    LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
 
Reading mysql slow query log from /data/logs/mysql/slowquery.log
Count: 1  Time=5.19s (5s)  Lock=3.02s (3s)  Rows=0.0 (0), root[root]@localhost
  DELETE FROM `wp_options` WHERE `option_name` = 'S'
 
Count: 1  Time=2.82s (2s)  Lock=0.20s (0s)  Rows=4064.0 (4064), root[root]@localhost
  SELECT TABLE_SCHEMA, TABLE_NAME, COLUMN_NAME, CHARACTER_SET_NAME,
  COLLATION_NAME, COLUMN_TYPE, IS_NULLABLE, EXTRA
  FROM INFORMATION_SCHEMA.COLUMNS where name  like "jack"
 
 
2.使用show profiles分析SQL性能
 
mysql> select version();
+-----------+
| version() |
+-----------+
| 5.7.22    |
+-----------+
1 row in set (0.01 sec)
 
创建SQL
CREATE TABLE `user` (
  `id` int(11) unsigned NOT NULL AUTO_INCREMENT,
  `name` varchar(32) NOT NULL DEFAULT '' COMMENT '姓名',
  `age` tinyint(4) NOT NULL COMMENT '年纪',
  `sex` tinyint(4) NOT NULL COMMENT '性别',
  `email` varchar(32) NOT NULL DEFAULT '' COMMENT '邮箱',
  `ctime` int(11) NOT NULL COMMENT '创建时间',
  PRIMARY KEY (`id`),
  KEY `index_email` (`email`(7))
) ENGINE=InnoDB AUTO_INCREMENT=4 DEFAULT CHARSET=utf8mb4;
 
INSERT INTO `user` (`id`, `name`, `age`, `sex`, `email`, `ctime`)
VALUES
    (1, '张三', 12, 1, 'zhangsan@qq.com', 1554789573),
    (2, '李四', 34, 2, 'zhangsansi@qq.com', 1554789573),
    (3, '王五', 90, 1, 'zhangsanlius@qq.com', 1554789573);
 
 
mysql> show variables like "%profiling%";
+------------------------+-------+
| Variable_name          | Value |
+------------------------+-------+
| have_profiling         | YES   |
| profiling              | ON    |
| profiling_history_size | 15    |
+------------------------+-------+
 
mysql> set profiling=1;
 
执行查询sql
mysql> select * from user where email='zhangsan@qq.com';
+----+--------+-----+-----+-----------------+------------+
| id | name   | age | sex | email           | ctime      |
+----+--------+-----+-----+-----------------+------------+
|  1 | 张三   |  12 |   1 | zhangsan@qq.com | 1554789573 |
+----+--------+-----+-----+-----------------+------------+
1 row in set (0.00 sec)
 
查看最近一条sql耗时
ysql> show profile;
+----------------------+----------+
| Status               | Duration |
+----------------------+----------+
| starting             | 0.000124 |
| checking permissions | 0.000012 |
| Opening tables       | 0.000017 |
| init                 | 0.000039 |
| System lock          | 0.000010 |
| optimizing           | 0.000015 |
| statistics           | 0.000060 |
| preparing            | 0.000016 |
| executing            | 0.000005 |
| Sending data         | 0.000045 |
| end                  | 0.000007 |
| query end            | 0.000009 |
| closing tables       | 0.000009 |
| freeing items        | 0.000023 |
| cleaning up          | 0.000012 |
+----------------------+----------+
15 rows in set, 1 warning (0.00 sec)
 
 
mysql> show profiles;
+----------+------------+------------------------------------------------------+
| Query_ID | Duration   | Query                                                |
+----------+------------+------------------------------------------------------+
|        4 | 0.00786300 | show tables                                          |
|        5 | 0.00459300 | show create table user                               |
|        6 | 0.00554100 | select * from user                                   |
|        7 | 0.01527800 | select * from user where email='zhangsan@qq.com'     |
|        8 | 0.00891700 | show profiles cpu,block,io for query 7               |
|        9 | 0.00007800 | show profile cpu,block,io for query 7                |
|       10 | 0.00009000 | select * from user where email='zhangsan@qq.com'
；  |
|       11 | 0.00051500 | select * from user where email='zhangsan@qq.com'     |
|       12 | 0.00009200 | set profiling=1
show profiles                        |
|       13 | 0.00913900 | show variables like "profile"                        |
|       14 | 0.01532300 | show variables like "%profile%"                      |
|       15 | 0.00814100 | show variables like "%profiles%"                     |
|       16 | 0.00808300 | show variables like "%profiling%"                    |
|       17 | 0.00957700 | show variables like "profiling"                      |
|       18 | 0.00040300 | select * from user where email='zhangsan@qq.com'     |
+----------+------------+------------------------------------------------------+
15 rows in set, 1 warning (0.00 sec)
 
查看指定的一条sql,获取cpu和block io的时间消耗
mysql> show profile cpu,block io for query 18;
+----------------------+----------+----------+------------+--------------+---------------+
| Status               | Duration | CPU_user | CPU_system | Block_ops_in | Block_ops_out |
+----------------------+----------+----------+------------+--------------+---------------+
| starting             | 0.000124 | 0.000073 |   0.000052 |            0 |             0 |
| checking permissions | 0.000012 | 0.000006 |   0.000005 |            0 |             0 |
| Opening tables       | 0.000017 | 0.000015 |   0.000002 |            0 |             0 |
| init                 | 0.000039 | 0.000037 |   0.000001 |            0 |             0 |
| System lock          | 0.000010 | 0.000009 |   0.000002 |            0 |             0 |
| optimizing           | 0.000015 | 0.000013 |   0.000002 |            0 |             0 |
| statistics           | 0.000060 | 0.000059 |   0.000001 |            0 |             0 |
| preparing            | 0.000016 | 0.000013 |   0.000003 |            0 |             0 |
| executing            | 0.000005 | 0.000003 |   0.000002 |            0 |             0 |
| Sending data         | 0.000045 | 0.000044 |   0.000001 |            0 |             0 |
| end                  | 0.000007 | 0.000004 |   0.000003 |            0 |             0 |
| query end            | 0.000009 | 0.000007 |   0.000001 |            0 |             0 |
| closing tables       | 0.000009 | 0.000008 |   0.000002 |            0 |             0 |
| freeing items        | 0.000023 | 0.000013 |   0.000010 |            0 |             0 |
| cleaning up          | 0.000012 | 0.000011 |   0.000009 |            0 |             0 |
+----------------------+----------+----------+------------+--------------+---------------+
15 rows in set, 1 warning (0.00 sec)
 
ALL    ---   显示所有的开销信息
BLOCK  IO   ---   显示块IO相关开销
CONTEXT  SWITCHES   ---   上下文切换相关开销
CPU   ---   显示CPU相关开销信息
IPC   ---   显示发送和接受相关开销信息
 MEMORY   ---   显示内存相关开销信息
PAGE  FAULTS   ---   显示页面错误相关开销信息
SOURCE   ---    显示和Source_function  ,  Source_file  ,  Source_line相关的开销信息
SWAPS   ---   显示交换次数相关开销的信息
 
 
查看告警是啥?
mysql> show warnings;
+-------+------+-----------------------------------------------------------------------------------------------------------------------------------------------------------+
| Level | Code | Message                                                                                                                                                   |
+-------+------+-----------------------------------------------------------------------------------------------------------------------------------------------------------+
| Error | 1064 | You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'warning' at line 1 |
+-------+------+-----------------------------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.01 sec)

3.使用Explain

https://blog.csdn.net/zsx1573...

查看mysql 日志信息

mysql> show variables like "%log%";
+-----------------------------------------+--------------------------------+
| Variable_name                           | Value                          |
+-----------------------------------------+--------------------------------+
| back_log                                | 80                             |
| binlog_cache_size                       | 32768                          |
| binlog_checksum                         | CRC32                          |
| binlog_direct_non_transactional_updates | OFF                            |
| binlog_error_action                     | IGNORE_ERROR                   |
| binlog_format                           | MIXED                          |
| binlog_gtid_simple_recovery             | OFF                            |
| binlog_max_flush_queue_time             | 0                              |
| binlog_order_commits                    | ON                             |
| binlog_row_image                        | FULL                           |
| binlog_rows_query_log_events            | OFF                            |
| binlog_stmt_cache_size                  | 32768                          |
| binlogging_impossible_mode              | IGNORE_ERROR                   |
| expire_logs_days                        | 30                             |
| general_log                             | OFF                            |
| general_log_file                        | /data/mysql/iZ257v6fpmnZ.log   |
| innodb_api_enable_binlog                | OFF                            |
| innodb_flush_log_at_timeout             | 1                              |
| innodb_flush_log_at_trx_commit          | 1  # 在事务提交时innodb是否同步日志从缓冲到文件中1表示事务以提交就同步不提交每隔一秒同步一次，性能会很差造成大量的磁盘I/O；定义为2表示只有在事务提交时才会同步但是可能会丢失整个事务                            |
| innodb_locks_unsafe_for_binlog          | OFF                            |
| innodb_log_buffer_size                  | 8388608                        |
| innodb_log_compressed_pages             | ON                             |
| innodb_log_file_size                    | 50331648                       |
| innodb_log_files_in_group               | 2                              |
| innodb_log_group_home_dir               | ./                             |
| innodb_mirrored_log_groups              | 1                              |
| innodb_online_alter_log_max_size        | 134217728                      |
| innodb_undo_logs                        | 128                            |
| log_bin                                 | ON                             |
| log_bin_basename                        | /data/mysql/mysql-bin          |
| log_bin_index                           | /data/mysql/mysql-bin.index    |
| log_bin_trust_function_creators         | OFF                            |
| log_bin_use_v1_row_events               | OFF                            |
| log_error                               | /data/logs/mysql/error.log     |
| log_output                              | FILE                           |
| log_queries_not_using_indexes           | OFF                            |
| log_slave_updates                       | OFF                            |
| log_slow_admin_statements               | OFF                            |
| log_slow_slave_statements               | OFF                            |
| log_throttle_queries_not_using_indexes  | 0                              |
| log_warnings                            | 1                              |
| max_binlog_cache_size                   | 18446744073709547520           |
| max_binlog_size                         | 1073741824                     |
| max_binlog_stmt_cache_size              | 18446744073709547520           |
| max_relay_log_size                      | 0                              |
| relay_log                               |                                |
| relay_log_basename                      |                                |
| relay_log_index                         |                                |
| relay_log_info_file                     | relay-log.info                 |
| relay_log_info_repository               | FILE                           |
| relay_log_purge                         | ON                             |
| relay_log_recovery                      | OFF                            |
| relay_log_space_limit                   | 0                              |
| simplified_binlog_gtid_recovery         | OFF                            |
| slow_query_log                          | ON                             |
| slow_query_log_file                     | /data/logs/mysql/slowquery.log |
| sql_log_bin                             | ON                             |
| sql_log_off                             | OFF                            |
| sync_binlog                             | 0                              |
| sync_relay_log                          | 10000                          |
| sync_relay_log_info                     | 10000                          |
+-----------------------------------------+--------------------------------+

mysql的server端日志

1.error_log 错误日志 2 . binlog 二进制日志 3.general_log 全局查询日志 4. slow_query_log 慢查询日志 5.relay_log 中继日志

存储引擎端日志

以innodb为例:

mysql> show table status from test where name='user'\G
*************************** 1. row ***************************
           Name: user
         Engine: InnoDB
        Version: 10
     Row_format: Dynamic
           Rows: 303
 Avg_row_length: 54
    Data_length: 16384
Max_data_length: 0
   Index_length: 16384
      Data_free: 0
 Auto_increment: 304
    Create_time: 2019-04-13 23:13:55
    Update_time: 2019-04-13 23:15:47
     Check_time: NULL
      Collation: utf8mb4_general_ci
       Checksum: NULL
 Create_options:
        Comment:
1 row in set (0.00 sec)

事务日志

redo log/undo log

物理文件:.frm 表结构 索引和数据在一起: 第一种, .ibdata1 共享表空间的信息共享表 ,第二种, 独享表空间table.iba

https://www.cnblogs.com/clsn/...

今天关于《mysql性能分析诊断》的内容介绍就到此结束，如果有什么疑问或者建议，可以在golang学习网公众号下多多回复交流；文中若有不正之处，也希望回复留言以告知！

mysql MySQL
版本声明
本文转载于：SegmentFault 如有侵犯，请联系study_golang@163.com删除
亲测-ubuntu20.04 安装 MySQL5.7亲测-ubuntu20.04 安装 MySQL5.7
上一篇
亲测-ubuntu20.04 安装 MySQL5.7
mysql Innodb存储引擎
下一篇
mysql Innodb存储引擎
查看更多
最新文章
查看更多
课程推荐
  • 前端进阶之JavaScript设计模式
    前端进阶之JavaScript设计模式
    设计模式是开发人员在软件开发过程中面临一般问题时的解决方案，代表了最佳的实践。本课程的主打内容包括JS常见设计模式以及具体应用场景，打造一站式知识长龙服务，适合有JS基础的同学学习。
    542次学习
  • GO语言核心编程课程
    GO语言核心编程课程
    本课程采用真实案例，全面具体可落地，从理论到实践，一步一步将GO核心编程技术、编程思想、底层实现融会贯通，使学习者贴近时代脉搏，做IT互联网时代的弄潮儿。
    508次学习
  • 简单聊聊mysql8与网络通信
    简单聊聊mysql8与网络通信
    如有问题加微信：Le-studyg；在课程中，我们将首先介绍MySQL8的新特性，包括性能优化、安全增强、新数据类型等，帮助学生快速熟悉MySQL8的最新功能。接着，我们将深入解析MySQL的网络通信机制，包括协议、连接管理、数据传输等，让
    497次学习
  • JavaScript正则表达式基础与实战
    JavaScript正则表达式基础与实战
    在任何一门编程语言中,正则表达式,都是一项重要的知识,它提供了高效的字符串匹配与捕获机制,可以极大的简化程序设计。
    487次学习
  • 从零制作响应式网站—Grid布局
    从零制作响应式网站—Grid布局
    本系列教程将展示从零制作一个假想的网络科技公司官网，分为导航，轮播，关于我们，成功案例，服务流程，团队介绍，数据部分，公司动态，底部信息等内容区块。网站整体采用CSSGrid布局，支持响应式，有流畅过渡和展现动画。
    484次学习
查看更多
AI推荐
  • 笔灵AI生成答辩PPT：高效制作学术与职场PPT的利器
    笔灵AI生成答辩PPT
    探索笔灵AI生成答辩PPT的强大功能，快速制作高质量答辩PPT。精准内容提取、多样模板匹配、数据可视化、配套自述稿生成，让您的学术和职场展示更加专业与高效。
    16次使用
  • 知网AIGC检测服务系统：精准识别学术文本中的AI生成内容
    知网AIGC检测服务系统
    知网AIGC检测服务系统，专注于检测学术文本中的疑似AI生成内容。依托知网海量高质量文献资源，结合先进的“知识增强AIGC检测技术”，系统能够从语言模式和语义逻辑两方面精准识别AI生成内容，适用于学术研究、教育和企业领域，确保文本的真实性和原创性。
    24次使用
  • AIGC检测服务：AIbiye助力确保论文原创性
    AIGC检测-Aibiye
    AIbiye官网推出的AIGC检测服务，专注于检测ChatGPT、Gemini、Claude等AIGC工具生成的文本，帮助用户确保论文的原创性和学术规范。支持txt和doc(x)格式，检测范围为论文正文，提供高准确性和便捷的用户体验。
    30次使用
  • 易笔AI论文平台：快速生成高质量学术论文的利器
    易笔AI论文
    易笔AI论文平台提供自动写作、格式校对、查重检测等功能，支持多种学术领域的论文生成。价格优惠，界面友好，操作简便，适用于学术研究者、学生及论文辅导机构。
    42次使用
  • 笔启AI论文写作平台：多类型论文生成与多语言支持
    笔启AI论文写作平台
    笔启AI论文写作平台提供多类型论文生成服务，支持多语言写作，满足学术研究者、学生和职场人士的需求。平台采用AI 4.0版本，确保论文质量和原创性，并提供查重保障和隐私保护。
    35次使用
查看更多
相关文章
关于我们 免责声明 意见反馈 联系我们 内容提交
Golang学习网：公益在线Go学习平台，帮助Go学习者快速成长！
技术交流群
Copyright 2023 http://www.17golang.com/ All Rights Reserved ｜ 苏ICP备2023003363号-1
  • Golang学习网
    关注公众号
    Golang学习网
微信登录更方便
  • 密码登录
  • 注册账号
忘记密码
登录即同意 用户协议 和 隐私政策
返回登录
  • 重置密码
发送验证码