SELECT data_key, data_value
FROM xf_data_registry
WHERE data_key IN ('options', 'languages', 'contentTypes', 'codeEventListeners', 'deferredRun', 'simpleCache', 'addOns', 'defaultStyleProperties', 'routeFiltersIn', 'routeFiltersOut', 'routesPublic', 'nodeTypes', 'bannedIps', 'discouragedIps', 'styles', 'displayStyles', 'userBanners', 'smilies', 'bbCode', 'threadPrefixes', 'userTitleLadder', 'reportCounts', 'moderationCounts', 'userModerationCounts', 'notices', 'userFieldsInfo')Run Time: 0.000802
| Select Type | Table | Type | Possible Keys | Key | Key Len | Ref | Rows | Extra |
|---|
| SIMPLE | xf_data_registry | range | PRIMARY | PRIMARY | 27 | | 26 | Using where |
SELECT data_key, data_value
FROM xf_data_registry
WHERE data_key IN ('brListenerClasses', 'brBriviumAddOns')Run Time: 0.000156
| Select Type | Table | Type | Possible Keys | Key | Key Len | Ref | Rows | Extra |
|---|
| SIMPLE | xf_data_registry | range | PRIMARY | PRIMARY | 27 | | 2 | Using where |
SELECT *
FROM xf_brivium_addon
ORDER BY addon_id
Run Time: 0.000142
| Select Type | Table | Type | Possible Keys | Key | Key Len | Ref | Rows | Extra |
|---|
| SIMPLE | xf_brivium_addon | index | | PRIMARY | 77 | | 1 | |
INSERT INTO xf_data_registry
(data_key, data_value)
VALUES
(?, ?)
ON DUPLICATE KEY UPDATE
data_value = VALUES(data_value)
Params: brBriviumAddOns, a:0:{}
Run Time: 0.000131
SELECT session_data
FROM xf_session
WHERE session_id = ?
AND expiry_date >= ?
Params: 6e914b8cdae264c0f975774d4589016d, 1716167549
Run Time: 0.000168
| Select Type | Table | Type | Possible Keys | Key | Key Len | Ref | Rows | Extra |
|---|
| SIMPLE | xf_session | const | PRIMARY,expiry_date | PRIMARY | 34 | const | 1 | |
SELECT cache_value
FROM xf_permission_combination
WHERE permission_combination_id = ?
Params: 1
Run Time: 0.000137
| Select Type | Table | Type | Possible Keys | Key | Key Len | Ref | Rows | Extra |
|---|
| SIMPLE | xf_permission_combination | const | PRIMARY | PRIMARY | 4 | const | 1 | |
SELECT thread.*
,
user.gender, user.avatar_date, user.gravatar,
NULL AS thread_read_date,
0 AS thread_reply_banned,
0 AS thread_is_watched,
'' AS draft_message, NULL AS draft_extra
FROM xf_thread AS thread
LEFT JOIN xf_user AS user ON
(user.user_id = thread.user_id)
WHERE thread.thread_id = ?
Params: 371704
Run Time: 0.000416
| Select Type | Table | Type | Possible Keys | Key | Key Len | Ref | Rows | Extra |
|---|
| SIMPLE | thread | const | PRIMARY | PRIMARY | 4 | const | 1 | |
| SIMPLE | user | const | PRIMARY | PRIMARY | 4 | const | 1 | |
SELECT node.*, forum.*
,
permission.cache_value AS node_permission_cache,
NULL AS forum_read_date
FROM xf_forum AS forum
INNER JOIN xf_node AS node ON (node.node_id = forum.node_id)
LEFT JOIN xf_permission_cache_content AS permission
ON (permission.permission_combination_id = 1
AND permission.content_type = 'node'
AND permission.content_id = forum.node_id)
WHERE node.node_id = ?
Params: 25
Run Time: 0.000357
| Select Type | Table | Type | Possible Keys | Key | Key Len | Ref | Rows | Extra |
|---|
| SIMPLE | forum | const | PRIMARY | PRIMARY | 4 | const | 1 | |
| SIMPLE | node | const | PRIMARY | PRIMARY | 4 | const | 1 | |
| SIMPLE | permission | const | PRIMARY | PRIMARY | 35 | const,const,const | 1 | |
SELECT post.*
,
thread.*, thread.user_id AS thread_user_id, thread.username AS thread_username,
thread.post_date AS thread_post_date,
post.user_id, post.username, post.post_date,
bb_code_parse_cache.parse_tree AS message_parsed, bb_code_parse_cache.cache_version AS message_cache_version,
user.*, IF(user.username IS NULL, post.username, user.username) AS username,
user_profile.*,
user_privacy.*,
signature_parse_cache.parse_tree AS signature_parsed, bb_code_parse_cache.cache_version AS signature_cache_version,
session_activity.view_date AS last_view_date,
0 AS like_date
FROM xf_post AS post
INNER JOIN xf_thread AS thread ON
(thread.thread_id = post.thread_id)
LEFT JOIN xf_bb_code_parse_cache AS bb_code_parse_cache ON
(bb_code_parse_cache.content_type = 'post' AND bb_code_parse_cache.content_id = post.post_id)
LEFT JOIN xf_user AS user ON
(user.user_id = post.user_id)
LEFT JOIN xf_user_profile AS user_profile ON
(user_profile.user_id = post.user_id)
LEFT JOIN xf_user_privacy AS user_privacy ON
(user_privacy.user_id = post.user_id)
LEFT JOIN xf_bb_code_parse_cache AS signature_parse_cache ON
(signature_parse_cache.content_type = 'signature' AND signature_parse_cache.content_id = post.user_id)
LEFT JOIN xf_session_activity AS session_activity ON
(post.user_id > 0 AND session_activity.user_id = post.user_id AND session_activity.unique_key = CAST(post.user_id AS BINARY))
WHERE (
(post.thread_id = ? AND (post.position >= 0 AND post.position < 10) )
)
AND (post.message_state IN ('visible'))
ORDER BY post.position ASC, post.post_date ASCParams: 371704
Run Time: 0.002599
| Select Type | Table | Type | Possible Keys | Key | Key Len | Ref | Rows | Extra |
|---|
| SIMPLE | thread | const | PRIMARY | PRIMARY | 4 | const | 1 | Using filesort |
| SIMPLE | post | ref | thread_id_post_date,thread_id_position | thread_id_post_date | 4 | const | 1 | Using index condition; Using where |
| SIMPLE | bb_code_parse_cache | eq_ref | content_type_id | content_type_id | 31 | const,xenforo.cc.post.post_id | 1 | Using where |
| SIMPLE | user | eq_ref | PRIMARY | PRIMARY | 4 | xenforo.cc.post.user_id | 1 | |
| SIMPLE | user_profile | eq_ref | PRIMARY | PRIMARY | 4 | xenforo.cc.post.user_id | 1 | |
| SIMPLE | user_privacy | eq_ref | PRIMARY | PRIMARY | 4 | xenforo.cc.post.user_id | 1 | |
| SIMPLE | signature_parse_cache | eq_ref | content_type_id | content_type_id | 31 | const,xenforo.cc.post.user_id | 1 | Using where |
| SIMPLE | session_activity | eq_ref | PRIMARY | PRIMARY | 22 | xenforo.cc.post.user_id,func | 1 | Using where |
INSERT INTO xf_thread_view
(thread_id)
VALUES
(?)
Params: 371704
Run Time: 0.000087
UPDATE `xf_session` SET `expiry_date` = ? WHERE (session_id = '6e914b8cdae264c0f975774d4589016d')
Params: 1716171149
Run Time: 0.000846
INSERT INTO xf_session_activity
(user_id, unique_key, ip, controller_name, controller_action, view_state, params, view_date, robot_key)
VALUES
(?, ?, ?, ?, ?, ?, ?, ?, ?)
ON DUPLICATE KEY UPDATE
ip = VALUES(ip),
controller_name = VALUES(controller_name),
controller_action = VALUES(controller_action),
view_state = VALUES(view_state),
params = VALUES(params),
view_date = VALUES(view_date),
robot_key = VALUES(robot_key)
Params: 0, , , XenForo_ControllerPublic_Thread, Index, valid, thread_id=371704, 1716167549,
Run Time: 0.000111
INSERT INTO xf_bb_code_parse_cache
(content_type, content_id, parse_tree, cache_version, cache_date)
VALUES (?, ?, ?, ?, ?)
ON DUPLICATE KEY UPDATE parse_tree = VALUES(parse_tree),
cache_version = VALUES(cache_version),
cache_date = VALUES(cache_date)
Params: post, 378340, a:18:{i:0;s:316:"CES 2021期间，三大芯片巨头同时在笔记本尤其是游戏本上更新换代。AMD带来了Zen3架构的锐龙5000U、锐龙5000H系列处理器，NVIDIA奉上了Ampere架构的RTX 30系列显卡，Intel则推出了首次应用10nm工艺和新架构的Tiger Lake-H 11代酷睿H系列处理器。
不过，";i:1;a:4:{s:3:"tag";s:1:"b";s:6:"option";N;s:8:"original";a:2:{i:0;s:3:"[B]";i:1;s:4:"[/B]";}s:8:"children";a:1:{i:0;s:139:"Intel首批发布的只是Tiger Lake-H35版本，热设计功耗均为35W，本质上就是Tiger Lake-U系列拉高功耗和频率的产物";}}i:2;s:129:"，只有4核心8线程，最高加速频率单核5.0GHz，只出现在一些创作本、轻薄游戏本中。
Intel还透露，";i:3;a:4:{s:3:"tag";s:1:"b";s:6:"option";N;s:8:"original";a:2:{i:0;s:3:"[B]";i:1;s:4:"[/B]";}s:8:"children";a:1:{i:0;s:252:"后续会推出更高端的Tiger Lake-H45版本，热设计功耗达到45W，最多8核心16线程，可以多个核心同时加速到5GHz，提供20条PCIe 4.0通道，还支持Wi-Fi 6/6E、Thunderbolt 4，真正适合高性能游戏本、设计本。";}}i:4;s:65:"
只是，Intel并没有说Tiger Lake-H45到底何时发布。
";i:5;a:4:{s:3:"tag";s:3:"url";s:6:"option";s:66:"https://static.cnbetacdn.com/article/2021/0128/0d0a769706746e3.jpg";s:8:"original";a:2:{i:0;s:74:"[URL='https://static.cnbetacdn.com/article/2021/0128/0d0a769706746e3.jpg']";i:1;s:6:"[/URL]";}s:8:"children";a:1:{i:0;a:4:{s:3:"tag";s:3:"img";s:6:"option";N;s:8:"original";a:2:{i:0;s:5:"[IMG]";i:1;s:6:"[/IMG]";}s:8:"children";a:1:{i:0;s:96:"https://rdimg.com/proxy/https://static.cnbetacdn.com/thumb/article/2021/0128/0d0a769706746e3.jpg";}}}}i:6;s:158:"
德国游戏本厂商XMG透露了一些蛛丝马迹，称只有Tiger Lake-H45 6/8核心处理器发布后，XMG游戏本才会跟进到11代酷睿H平台，";i:7;a:4:{s:3:"tag";s:1:"b";s:6:"option";N;s:8:"original";a:2:{i:0;s:3:"[B]";i:1;s:4:"[/B]";}s:8:"children";a:1:{i:0;s:33:"预计在今年第二季度末。";}}i:8;s:17:"
这意味着，";i:9;a:4:{s:3:"tag";s:1:"b";s:6:"option";N;s:8:"original";a:2:{i:0;s:3:"[B]";i:1;s:4:"[/B]";}s:8:"children";a:1:{i:0;s:170:"Tiger Lake-H45会在5-6月份推出，而考虑到6月初是一年一度的台北电脑展(今年已确定回归)，然后就是618大促，这个时间节点刚刚好。";}}i:10;s:166:"
另外，AnandTech也报道称，Intel告诉他们，Tiger Lake-H45处理器会在第一季度量产并出货，意味着第二季度上市。
Tiger Lake-H35只有";i:11;a:4:{s:3:"tag";s:1:"b";s:6:"option";N;s:8:"original";a:2:{i:0;s:3:"[B]";i:1;s:4:"[/B]";}s:8:"children";a:1:{i:0;s:32:"i5-11300、i7-11370H、i7-11375H";}}i:12;s:65:"三款型号，Tiger Lake-H45则已经流出四款型号，包括";i:13;a:4:{s:3:"tag";s:1:"b";s:6:"option";N;s:8:"original";a:2:{i:0;s:3:"[B]";i:1;s:4:"[/B]";}s:8:"children";a:1:{i:0;s:187:"6核心12线程的i5-11400H，8核心16线程的i7-11800H、i9-11900H、i9-11980HK，最后一款旗舰有望支持双核同时加速到5.0GHz，但热设计功耗可能也会超过45W。";}}i:14;s:17:"
目前，基于";i:15;a:4:{s:3:"tag";s:3:"url";s:6:"option";s:77:"https://c.duomai.com/track.php?site_id=242986&euid=&t=https://amd-cpu.jd.com/";s:8:"original";a:2:{i:0;s:85:"[URL='https://c.duomai.com/track.php?site_id=242986&euid=&t=https://amd-cpu.jd.com/']";i:1;s:6:"[/URL]";}s:8:"children";a:1:{i:0;s:3:"AMD";}}i:16;s:132:"锐龙5000H的高性能游戏本正在集体登场，Intel这边则还要等上差不多半年，才能拿出同样的产品线。
";i:17;a:4:{s:3:"tag";s:3:"url";s:6:"option";s:66:"https://static.cnbetacdn.com/article/2021/0128/da5dfb6d8934fde.png";s:8:"original";a:2:{i:0;s:74:"[URL='https://static.cnbetacdn.com/article/2021/0128/da5dfb6d8934fde.png']";i:1;s:6:"[/URL]";}s:8:"children";a:1:{i:0;a:4:{s:3:"tag";s:3:"img";s:6:"option";N;s:8:"original";a:2:{i:0;s:5:"[IMG]";i:1;s:6:"[/IMG]";}s:8:"children";a:1:{i:0;s:96:"https://rdimg.com/proxy/https://static.cnbetacdn.com/thumb/article/2021/0128/da5dfb6d8934fde.png";}}}}}, 1621686945, 1716167549
Run Time: 0.000751