历史详情

Run ID: 20260827-204844-5793ab55

返回历史

测试结果

Run ID: 20260827-204844-5793ab55

导出 JSON
总请求45
成功 / 失败35/10
成功率77.78%
平均延迟5070 ms
P95 / Tokens6544 / 4171
渠道模型成功失败成功率失败率稳定性平均延迟 msP95 msTokens首个错误
DeepSeek-v4-pro-04 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1239 1514 339
DeepSeek-v4-pro-02 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1331 1599 339
DeepSeek-v4-pro-03 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1441 1681 339
DeepSeek-v4-pro-01 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1447 1510 339
Qwen3.8-Max qwen3.8-max 3/3 0/3 100.0% 0.0% 稳定 1997 2251 386
Kimi K3 - Aliyun Bailian kimi/kimi-k3 3/3 0/3 100.0% 0.0% 稳定 2769 3601 345
qwen3.6-plus qwen3.6-plus 3/3 0/3 100.0% 0.0% 可用 4636 5773 778
腾讯 Gemini 3.5 Flash gemini-3.5-flash 3/3 0/3 100.0% 0.0% 可用 4780 5364 78
Kimi K3 kimi-k3 3/3 0/3 100.0% 0.0% 可用 4984 6544 345
yulin-gemini-3.7-flash-high gemini-3.7-flash-high 3/3 0/3 100.0% 0.0% 可用 6017 7597 482
Kimi K3 - TopenRouter kimi-k3 3/3 0/3 100.0% 0.0% 可用 25802 70354 348
jd-gemini-3.1-pro-preview gemini-3.1-pro-preview 2/3 1/3 66.67% 33.33% 不稳定 4054 5545 53 timeout: The read operation timed out
MiniMax H3 Context IR MiniMax-H3 0/3 3/3 0.0% 100.0% 不稳定 - - 0 HTTP 400: binding: expr_path=content, cause=missing required parameter
pixflow-gemini-3.1-pro-preview gemini-3.1-pro-preview 0/3 3/3 0.0% 100.0% 不稳定 - - 0 HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
yuling-gpt-5.5 gpt-5.5 0/3 3/3 0.0% 100.0% 不稳定 - - 0 HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}

结果明细

#1 DeepSeek-v4-pro-01 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1364 ms Tokens:113 时间:2026-08-27 20:46:42
JSON
无输出内容。
#2 DeepSeek-v4-pro-01 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1468 ms Tokens:113 时间:2026-08-27 20:46:42
JSON
无输出内容。
#3 DeepSeek-v4-pro-01 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1510 ms Tokens:113 时间:2026-08-27 20:46:44
JSON
无输出内容。
#4 DeepSeek-v4-pro-03 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1594 ms Tokens:113 时间:2026-08-27 20:46:44
JSON
无输出内容。
#5 DeepSeek-v4-pro-03 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1050 ms Tokens:113 时间:2026-08-27 20:46:45
JSON
无输出内容。
#6 DeepSeek-v4-pro-03 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1681 ms Tokens:113 时间:2026-08-27 20:46:45
JSON
无输出内容。
#7 DeepSeek-v4-pro-04 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1019 ms Tokens:113 时间:2026-08-27 20:46:46
JSON
无输出内容。
#8 DeepSeek-v4-pro-04 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1514 ms Tokens:113 时间:2026-08-27 20:46:47
JSON
无输出内容。
#9 DeepSeek-v4-pro-04 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1186 ms Tokens:113 时间:2026-08-27 20:46:47
JSON
无输出内容。
#10 DeepSeek-v4-pro-02 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1168 ms Tokens:113 时间:2026-08-27 20:46:48
JSON
无输出内容。
#11 DeepSeek-v4-pro-02 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1599 ms Tokens:113 时间:2026-08-27 20:46:48
JSON
无输出内容。
#12 DeepSeek-v4-pro-02 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1227 ms Tokens:113 时间:2026-08-27 20:46:49
JSON
无输出内容。
#13 jd-gemini-3.1-pro-preview 成功 HTTP 200
模型:gemini-3.1-pro-preview 延迟:5545 ms Tokens:27 时间:2026-08-27 20:46:50
JSON
无输出内容。
#14 jd-gemini-3.1-pro-preview 成功 HTTP 200
模型:gemini-3.1-pro-preview 延迟:2564 ms Tokens:26 时间:2026-08-27 20:46:56
JSON
无输出内容。
#15 腾讯 Gemini 3.5 Flash 成功 HTTP 200
模型:gemini-3.5-flash 延迟:5364 ms Tokens:26 时间:2026-08-27 20:46:58
JSON
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning_content": "**My Internal Monologue on Summarizing and the User's Expertise**\n\nAlright, let's break down this request. The core task is to summarize a piece of text, but the crucial constraints are:\n\n1. **First-Person Perspective:** I need to inhabit the *thoughts* described in the text, speaking as if they are my own internal musings. This isn't about me *reporting* on the thoughts; it's about me *having* them.\n2. **Fulsome Summary of Thought Process:** This means I can't just give a brief overview. I need to go deep into the *how* and *why* of the thinking, detailing the steps, the considerations, the nuances. It’s about laying bare the entire intellectual journey.\n3. **Target Audience is Expert:** The user is an expert. This implies I can skip over foundational explanations and assume a sophisticated understanding of the subject matter. I don't need to dumb anything down; in fact, I should probably use precise language and acknowledge the inherent complexities they'd expect.\n4. **Specific Starting Header:** The summary *must* begin with a bolded header, and the example given is \"My Summary:\". I
#16 腾讯 Gemini 3.5 Flash 成功 HTTP 200
模型:gemini-3.5-flash 延迟:4233 ms Tokens:26 时间:2026-08-27 20:47:04
JSON
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning_content": "**My Internal Monologue: Navigating the Nuances of Expert Communication**\n\nAlright, so the core of this request is for me to summarize a given text, but with a very specific constraint: it needs to be in the first person, as if these thoughts are *my* own. And not just a brief summary, but a \"fulsome\" one, detailing the *entire* thought process. The target audience is an \"expert in their field,\" which is a crucial cue. This means I don't need to over-explain basic concepts. Instead, I should lean into the intellectual engagement, the critical analysis, and the strategic decision-making that goes into formulating a response suitable for someone who already possesses a deep understanding of the subject matter.\n\nLet's break down what \"fulsome\" really means in this context. It's not just about length; it's about depth and thoroughness. It implies a comprehensive exploration of how I arrived at the final output. For an expert, this would involve:\n\n* **Deconstructing the Input:** First, I need to meticulously dissect the provided text. What are its main arguments? What is the author's under
#17 腾讯 Gemini 3.5 Flash 成功 HTTP 200
模型:gemini-3.5-flash 延迟:4744 ms Tokens:26 时间:2026-08-27 20:47:08
JSON
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning_content": "**My Internal Monologue: Navigating the Nuances of Expert Communication**\n\nAlright, so the core of this request is for me to summarize a given text, but with a very specific constraint: it needs to be in the first person, as if these thoughts are *my* own. And not just a brief summary, but a \"fulsome\" one, detailing the *entire* thought process. The target audience is an \"expert in their field,\" which is a crucial cue. This means I don't need to over-explain basic concepts. Instead, I should lean into the intellectual engagement, the critical analysis, and the strategic decision-making that goes into formulating a response suitable for someone who already possesses a deep understanding of the subject matter.\n\nLet's break down what \"fulsome\" really means in this context. It's not just about length; it's about depth and thoroughness. It implies a comprehensive exploration of how I arrived at the final output. For an expert, this would involve:\n\n* **Deconstructing the Input:** First, I need to meticulously dissect the provided text. What are its main arguments? What is the author's under
#18 qwen3.6-plus 成功 HTTP 200
模型:qwen3.6-plus 延迟:5773 ms Tokens:322 时间:2026-08-27 20:47:13
JSON
{"status":"ok","message":"stable"}
#19 jd-gemini-3.1-pro-preview 失败 HTTP -
模型:gemini-3.1-pro-preview 延迟:30187 ms Tokens:- 时间:2026-08-27 20:46:51
JSON
timeout: The read operation timed out
#20 qwen3.6-plus 成功 HTTP 200
模型:qwen3.6-plus 延迟:4505 ms Tokens:259 时间:2026-08-27 20:47:18
JSON
{"status":"ok","message":"stable"}
#21 pixflow-gemini-3.1-pro-preview 失败 HTTP 403
模型:gemini-3.1-pro-preview 延迟:510 ms Tokens:- 时间:2026-08-27 20:47:23
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#22 pixflow-gemini-3.1-pro-preview 失败 HTTP 403
模型:gemini-3.1-pro-preview 延迟:525 ms Tokens:- 时间:2026-08-27 20:47:23
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#23 pixflow-gemini-3.1-pro-preview 失败 HTTP 403
模型:gemini-3.1-pro-preview 延迟:469 ms Tokens:- 时间:2026-08-27 20:47:24
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#24 qwen3.6-plus 成功 HTTP 200
模型:qwen3.6-plus 延迟:3631 ms Tokens:197 时间:2026-08-27 20:47:21
JSON
{"status":"ok","message":"stable"}
#25 yuling-gpt-5.5 失败 HTTP 403
模型:gpt-5.5 延迟:459 ms Tokens:- 时间:2026-08-27 20:47:24
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#26 yuling-gpt-5.5 失败 HTTP 403
模型:gpt-5.5 延迟:456 ms Tokens:- 时间:2026-08-27 20:47:24
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#27 yuling-gpt-5.5 失败 HTTP 403
模型:gpt-5.5 延迟:465 ms Tokens:- 时间:2026-08-27 20:47:25
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#28 Kimi K3 - Aliyun Bailian 成功 HTTP 200
模型:kimi/kimi-k3 延迟:2776 ms Tokens:115 时间:2026-08-27 20:47:25
JSON
无输出内容。
#29 Kimi K3 - Aliyun Bailian 成功 HTTP 200
模型:kimi/kimi-k3 延迟:3601 ms Tokens:115 时间:2026-08-27 20:47:25
JSON
无输出内容。
#30 Kimi K3 - Aliyun Bailian 成功 HTTP 200
模型:kimi/kimi-k3 延迟:1930 ms Tokens:115 时间:2026-08-27 20:47:28
JSON
无输出内容。
#31 Kimi K3 成功 HTTP 200
模型:kimi-k3 延迟:4400 ms Tokens:115 时间:2026-08-27 20:47:29
JSON
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply only with a specific JSON: {\"status\":\""}, "logprobs": null, "finish_reason": "length"}
#32 Kimi K3 成功 HTTP 200
模型:kimi-k3 延迟:4010 ms Tokens:115 时间:2026-08-27 20:47:30
JSON
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply with only a specific JSON: {\"status\":\""}, "logprobs": null, "finish_reason": "length"}
#33 Kimi K3 成功 HTTP 200
模型:kimi-k3 延迟:6544 ms Tokens:115 时间:2026-08-27 20:47:33
JSON
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply with only JSON: {\"status\":\"ok\",\""}, "logprobs": null, "finish_reason": "length"}
#34 Kimi K3 - TopenRouter 成功 HTTP 200
模型:kimi-k3 延迟:4029 ms Tokens:116 时间:2026-08-27 20:47:39
JSON
无输出内容。
#35 Kimi K3 - TopenRouter 成功 HTTP 200
模型:kimi-k3 延迟:3024 ms Tokens:116 时间:2026-08-27 20:47:44
JSON
无输出内容。
#36 Qwen3.8-Max 成功 HTTP 200
模型:qwen3.8-max 延迟:1833 ms Tokens:130 时间:2026-08-27 20:47:47
JSON
{"status":"ok","message":"stable"}
#37 Qwen3.8-Max 成功 HTTP 200
模型:qwen3.8-max 延迟:1907 ms Tokens:127 时间:2026-08-27 20:47:48
JSON
{"status":"ok","message":"stable"}
#38 Qwen3.8-Max 成功 HTTP 200
模型:qwen3.8-max 延迟:2251 ms Tokens:129 时间:2026-08-27 20:47:50
JSON
{"status":"ok","message":"stable"}
#39 MiniMax H3 Context IR 失败 HTTP 400
模型:MiniMax-H3 延迟:196 ms Tokens:- 时间:2026-08-27 20:47:53
JSON
HTTP 400: binding: expr_path=content, cause=missing required parameter
#40 MiniMax H3 Context IR 失败 HTTP 400
模型:MiniMax-H3 延迟:223 ms Tokens:- 时间:2026-08-27 20:47:53
JSON
HTTP 400: binding: expr_path=content, cause=missing required parameter
#41 MiniMax H3 Context IR 失败 HTTP 400
模型:MiniMax-H3 延迟:189 ms Tokens:- 时间:2026-08-27 20:47:53
JSON
HTTP 400: binding: expr_path=content, cause=missing required parameter
#42 yulin-gemini-3.7-flash-high 成功 HTTP 200
模型:gemini-3.7-flash-high 延迟:7597 ms Tokens:173 时间:2026-08-27 20:47:53
JSON
{"status":"ok","message":"stable"}
#43 yulin-gemini-3.7-flash-high 成功 HTTP 200
模型:gemini-3.7-flash-high 延迟:5475 ms Tokens:149 时间:2026-08-27 20:48:01
JSON
{"status":"ok","message":"stable"}
#44 yulin-gemini-3.7-flash-high 成功 HTTP 200
模型:gemini-3.7-flash-high 延迟:4980 ms Tokens:160 时间:2026-08-27 20:48:06
JSON
{"status":"ok","message":"stable"}
#45 Kimi K3 - TopenRouter 成功 HTTP 200
模型:kimi-k3 延迟:70354 ms Tokens:116 时间:2026-08-27 20:47:34
JSON
无输出内容。

表格明细

渠道状态延迟 msHTTPTokens输出 / 错误
DeepSeek-v4-pro-01 成功 1364 200 113
DeepSeek-v4-pro-01 成功 1468 200 113
DeepSeek-v4-pro-01 成功 1510 200 113
DeepSeek-v4-pro-03 成功 1594 200 113
DeepSeek-v4-pro-03 成功 1050 200 113
DeepSeek-v4-pro-03 成功 1681 200 113
DeepSeek-v4-pro-04 成功 1019 200 113
DeepSeek-v4-pro-04 成功 1514 200 113
DeepSeek-v4-pro-04 成功 1186 200 113
DeepSeek-v4-pro-02 成功 1168 200 113
DeepSeek-v4-pro-02 成功 1599 200 113
DeepSeek-v4-pro-02 成功 1227 200 113
jd-gemini-3.1-pro-preview 成功 5545 200 27
jd-gemini-3.1-pro-preview 成功 2564 200 26
腾讯 Gemini 3.5 Flash 成功 5364 200 26 {"index": 0, "message": {"role": "assistant", "content": null, "reasoning_content": "**My Internal Monologue on Summarizing and the User's Expertise**\n\nAlright, let's break down this request. The core task is to summarize a piece of text, but the crucial constraints are:\n\n1. **First-Person Perspective:** I need to inhabit the *thoughts* described in the text, speaking as if they are my own internal musings. This isn't about me *reporting* on the thoughts; it's about me *having* them.\n2. **Fulsome Summary of Thought Process:** This means I can't just give a brief overview. I need to go deep into the *how* and *why* of the thinking, detailing the steps, the considerations, the nuances. It’s about laying bare the entire intellectual journey.\n3. **Target Audience is Expert:** The user is an expert. This implies I can skip over foundational explanations and assume a sophisticated understanding of the subject matter. I don't need to dumb anything down; in fact, I should probably use precise language and acknowledge the inherent complexities they'd expect.\n4. **Specific Starting Header:** The summary *must* begin with a bolded header, and the example given is \"My Summary:\". I
腾讯 Gemini 3.5 Flash 成功 4233 200 26 {"index": 0, "message": {"role": "assistant", "content": null, "reasoning_content": "**My Internal Monologue: Navigating the Nuances of Expert Communication**\n\nAlright, so the core of this request is for me to summarize a given text, but with a very specific constraint: it needs to be in the first person, as if these thoughts are *my* own. And not just a brief summary, but a \"fulsome\" one, detailing the *entire* thought process. The target audience is an \"expert in their field,\" which is a crucial cue. This means I don't need to over-explain basic concepts. Instead, I should lean into the intellectual engagement, the critical analysis, and the strategic decision-making that goes into formulating a response suitable for someone who already possesses a deep understanding of the subject matter.\n\nLet's break down what \"fulsome\" really means in this context. It's not just about length; it's about depth and thoroughness. It implies a comprehensive exploration of how I arrived at the final output. For an expert, this would involve:\n\n* **Deconstructing the Input:** First, I need to meticulously dissect the provided text. What are its main arguments? What is the author's under
腾讯 Gemini 3.5 Flash 成功 4744 200 26 {"index": 0, "message": {"role": "assistant", "content": null, "reasoning_content": "**My Internal Monologue: Navigating the Nuances of Expert Communication**\n\nAlright, so the core of this request is for me to summarize a given text, but with a very specific constraint: it needs to be in the first person, as if these thoughts are *my* own. And not just a brief summary, but a \"fulsome\" one, detailing the *entire* thought process. The target audience is an \"expert in their field,\" which is a crucial cue. This means I don't need to over-explain basic concepts. Instead, I should lean into the intellectual engagement, the critical analysis, and the strategic decision-making that goes into formulating a response suitable for someone who already possesses a deep understanding of the subject matter.\n\nLet's break down what \"fulsome\" really means in this context. It's not just about length; it's about depth and thoroughness. It implies a comprehensive exploration of how I arrived at the final output. For an expert, this would involve:\n\n* **Deconstructing the Input:** First, I need to meticulously dissect the provided text. What are its main arguments? What is the author's under
qwen3.6-plus 成功 5773 200 322 {"status":"ok","message":"stable"}
jd-gemini-3.1-pro-preview 失败 30187 - - timeout: The read operation timed out
qwen3.6-plus 成功 4505 200 259 {"status":"ok","message":"stable"}
pixflow-gemini-3.1-pro-preview 失败 510 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
pixflow-gemini-3.1-pro-preview 失败 525 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
pixflow-gemini-3.1-pro-preview 失败 469 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
qwen3.6-plus 成功 3631 200 197 {"status":"ok","message":"stable"}
yuling-gpt-5.5 失败 459 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
yuling-gpt-5.5 失败 456 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
yuling-gpt-5.5 失败 465 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
Kimi K3 - Aliyun Bailian 成功 2776 200 115
Kimi K3 - Aliyun Bailian 成功 3601 200 115
Kimi K3 - Aliyun Bailian 成功 1930 200 115
Kimi K3 成功 4400 200 115 {"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply only with a specific JSON: {\"status\":\""}, "logprobs": null, "finish_reason": "length"}
Kimi K3 成功 4010 200 115 {"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply with only a specific JSON: {\"status\":\""}, "logprobs": null, "finish_reason": "length"}
Kimi K3 成功 6544 200 115 {"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply with only JSON: {\"status\":\"ok\",\""}, "logprobs": null, "finish_reason": "length"}
Kimi K3 - TopenRouter 成功 4029 200 116
Kimi K3 - TopenRouter 成功 3024 200 116
Qwen3.8-Max 成功 1833 200 130 {"status":"ok","message":"stable"}
Qwen3.8-Max 成功 1907 200 127 {"status":"ok","message":"stable"}
Qwen3.8-Max 成功 2251 200 129 {"status":"ok","message":"stable"}
MiniMax H3 Context IR 失败 196 400 - HTTP 400: binding: expr_path=content, cause=missing required parameter
MiniMax H3 Context IR 失败 223 400 - HTTP 400: binding: expr_path=content, cause=missing required parameter
MiniMax H3 Context IR 失败 189 400 - HTTP 400: binding: expr_path=content, cause=missing required parameter
yulin-gemini-3.7-flash-high 成功 7597 200 173 {"status":"ok","message":"stable"}
yulin-gemini-3.7-flash-high 成功 5475 200 149 {"status":"ok","message":"stable"}
yulin-gemini-3.7-flash-high 成功 4980 200 160 {"status":"ok","message":"stable"}
Kimi K3 - TopenRouter 成功 70354 200 116