历史详情

Run ID: 20260828-060020-0706754e

返回历史

测试结果

Run ID: 20260828-060020-0706754e

导出 JSON
总请求45
成功 / 失败36/9
成功率80.0%
平均延迟4262 ms
P95 / Tokens7154 / 4297
渠道模型成功失败成功率失败率稳定性平均延迟 msP95 msTokens首个错误
DeepSeek-v4-pro-03 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1075 1136 339
DeepSeek-v4-pro-01 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1287 1373 339
DeepSeek-v4-pro-02 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1502 1778 339
DeepSeek-v4-pro-04 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1504 1549 339
Qwen3.8-Max qwen3.8-max 3/3 0/3 100.0% 0.0% 稳定 1918 2134 390
jd-gemini-3.1-pro-preview gemini-3.1-pro-preview 3/3 0/3 100.0% 0.0% 稳定 2426 2497 79
Kimi K3 kimi-k3 3/3 0/3 100.0% 0.0% 稳定 3712 4351 345
qwen3.6-plus qwen3.6-plus 3/3 0/3 100.0% 0.0% 可用 4680 5324 774
腾讯 Gemini 3.5 Flash gemini-3.5-flash 3/3 0/3 100.0% 0.0% 可用 4880 5420 78
yulin-gemini-3.7-flash-high gemini-3.7-flash-high 3/3 0/3 100.0% 0.0% 可用 5036 5689 516
Kimi K3 - Aliyun Bailian kimi/kimi-k3 3/3 0/3 100.0% 0.0% 可用 5688 8807 345
Kimi K3 - TopenRouter kimi-k3 3/3 0/3 100.0% 0.0% 可用 17434 42998 414
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 延迟:1307 ms Tokens:113 时间:2026-08-28 05:58:57
JSON
无输出内容。
#2 DeepSeek-v4-pro-01 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1373 ms Tokens:113 时间:2026-08-28 05:58:57
JSON
无输出内容。
#3 DeepSeek-v4-pro-01 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1183 ms Tokens:113 时间:2026-08-28 05:58:58
JSON
无输出内容。
#4 DeepSeek-v4-pro-03 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1136 ms Tokens:113 时间:2026-08-28 05:58:58
JSON
无输出内容。
#5 DeepSeek-v4-pro-03 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1024 ms Tokens:113 时间:2026-08-28 05:58:59
JSON
无输出内容。
#6 DeepSeek-v4-pro-03 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1066 ms Tokens:113 时间:2026-08-28 05:58:59
JSON
无输出内容。
#7 DeepSeek-v4-pro-04 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1505 ms Tokens:113 时间:2026-08-28 05:59:00
JSON
无输出内容。
#8 DeepSeek-v4-pro-04 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1549 ms Tokens:113 时间:2026-08-28 05:59:00
JSON
无输出内容。
#9 DeepSeek-v4-pro-04 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1459 ms Tokens:113 时间:2026-08-28 05:59:02
JSON
无输出内容。
#10 DeepSeek-v4-pro-02 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1778 ms Tokens:113 时间:2026-08-28 05:59:02
JSON
无输出内容。
#11 DeepSeek-v4-pro-02 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1180 ms Tokens:113 时间:2026-08-28 05:59:03
JSON
无输出内容。
#12 DeepSeek-v4-pro-02 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1549 ms Tokens:113 时间:2026-08-28 05:59:04
JSON
无输出内容。
#13 jd-gemini-3.1-pro-preview 成功 HTTP 200
模型:gemini-3.1-pro-preview 延迟:2474 ms Tokens:26 时间:2026-08-28 05:59:04
JSON
无输出内容。
#14 jd-gemini-3.1-pro-preview 成功 HTTP 200
模型:gemini-3.1-pro-preview 延迟:2309 ms Tokens:26 时间:2026-08-28 05:59:05
JSON
无输出内容。
#15 jd-gemini-3.1-pro-preview 成功 HTTP 200
模型:gemini-3.1-pro-preview 延迟:2497 ms Tokens:27 时间:2026-08-28 05:59:07
JSON
无输出内容。
#16 腾讯 Gemini 3.5 Flash 成功 HTTP 200
模型:gemini-3.5-flash 延迟:4638 ms Tokens:26 时间:2026-08-28 05:59:07
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 延迟:5420 ms Tokens:26 时间:2026-08-28 05:59:09
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
#18 腾讯 Gemini 3.5 Flash 成功 HTTP 200
模型:gemini-3.5-flash 延迟:4582 ms Tokens:26 时间:2026-08-28 05:59:12
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
#19 qwen3.6-plus 成功 HTTP 200
模型:qwen3.6-plus 延迟:5324 ms Tokens:291 时间:2026-08-28 05:59:15
JSON
{"status":"ok","message":"stable"}
#20 qwen3.6-plus 成功 HTTP 200
模型:qwen3.6-plus 延迟:5035 ms Tokens:291 时间:2026-08-28 05:59:17
JSON
{"status":"ok","message":"stable"}
#21 pixflow-gemini-3.1-pro-preview 失败 HTTP 403
模型:gemini-3.1-pro-preview 延迟:529 ms Tokens:- 时间:2026-08-28 05:59:22
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#22 pixflow-gemini-3.1-pro-preview 失败 HTTP 403
模型:gemini-3.1-pro-preview 延迟:542 ms Tokens:- 时间:2026-08-28 05:59:22
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#23 pixflow-gemini-3.1-pro-preview 失败 HTTP 403
模型:gemini-3.1-pro-preview 延迟:465 ms Tokens:- 时间:2026-08-28 05:59:23
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#24 yuling-gpt-5.5 失败 HTTP 403
模型:gpt-5.5 延迟:517 ms Tokens:- 时间:2026-08-28 05:59:23
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#25 qwen3.6-plus 成功 HTTP 200
模型:qwen3.6-plus 延迟:3681 ms Tokens:192 时间:2026-08-28 05:59:20
JSON
{"status":"ok","message":"stable"}
#26 yuling-gpt-5.5 失败 HTTP 403
模型:gpt-5.5 延迟:421 ms Tokens:- 时间:2026-08-28 05:59:24
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#27 yuling-gpt-5.5 失败 HTTP 403
模型:gpt-5.5 延迟:522 ms Tokens:- 时间:2026-08-28 05:59:24
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#28 Kimi K3 - Aliyun Bailian 成功 HTTP 200
模型:kimi/kimi-k3 延迟:7154 ms Tokens:115 时间:2026-08-28 05:59:24
JSON
无输出内容。
#29 Kimi K3 - Aliyun Bailian 成功 HTTP 200
模型:kimi/kimi-k3 延迟:1103 ms Tokens:115 时间:2026-08-28 05:59:31
JSON
无输出内容。
#30 Kimi K3 - Aliyun Bailian 成功 HTTP 200
模型:kimi/kimi-k3 延迟:8807 ms Tokens:115 时间:2026-08-28 05:59:24
JSON
无输出内容。
#31 Kimi K3 成功 HTTP 200
模型:kimi-k3 延迟:4351 ms Tokens:115 时间:2026-08-28 05:59:32
JSON
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply only with JSON: {\"status\":\"ok\",\""}, "logprobs": null, "finish_reason": "length"}
#32 Kimi K3 成功 HTTP 200
模型:kimi-k3 延迟:3804 ms Tokens:115 时间:2026-08-28 05:59: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"}
#33 Kimi K3 成功 HTTP 200
模型:kimi-k3 延迟:2983 ms Tokens:115 时间:2026-08-28 05:59:37
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 延迟:4512 ms Tokens:144 时间:2026-08-28 05:59:40
JSON
{"status":"ok","message":"stable"}
#35 Kimi K3 - TopenRouter 成功 HTTP 200
模型:kimi-k3 延迟:4793 ms Tokens:155 时间:2026-08-28 05:59:44
JSON
{"status":"ok","message":"stable"}
#36 Qwen3.8-Max 成功 HTTP 200
模型:qwen3.8-max 延迟:2134 ms Tokens:147 时间:2026-08-28 05:59:49
JSON
{"status":"ok","message":"stable"}
#37 Qwen3.8-Max 成功 HTTP 200
模型:qwen3.8-max 延迟:1762 ms Tokens:124 时间:2026-08-28 05:59:51
JSON
{"status":"ok","message":"stable"}
#38 Qwen3.8-Max 成功 HTTP 200
模型:qwen3.8-max 延迟:1859 ms Tokens:119 时间:2026-08-28 05:59:53
JSON
{"status":"ok","message":"stable"}
#39 MiniMax H3 Context IR 失败 HTTP 400
模型:MiniMax-H3 延迟:240 ms Tokens:- 时间:2026-08-28 05:59:55
JSON
HTTP 400: binding: expr_path=content, cause=missing required parameter
#40 MiniMax H3 Context IR 失败 HTTP 400
模型:MiniMax-H3 延迟:199 ms Tokens:- 时间:2026-08-28 05:59:55
JSON
HTTP 400: binding: expr_path=content, cause=missing required parameter
#41 MiniMax H3 Context IR 失败 HTTP 400
模型:MiniMax-H3 延迟:194 ms Tokens:- 时间:2026-08-28 05:59:55
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 延迟:5223 ms Tokens:182 时间:2026-08-28 05:59:55
JSON
{"status":"ok","message":"stable"}
#43 yulin-gemini-3.7-flash-high 成功 HTTP 200
模型:gemini-3.7-flash-high 延迟:5689 ms Tokens:169 时间:2026-08-28 06:00:01
JSON
{"status":"ok","message":"stable"}
#44 yulin-gemini-3.7-flash-high 成功 HTTP 200
模型:gemini-3.7-flash-high 延迟:4197 ms Tokens:165 时间:2026-08-28 06:00:06
JSON
{"status":"ok","message":"stable"}
#45 Kimi K3 - TopenRouter 成功 HTTP 200
模型:kimi-k3 延迟:42998 ms Tokens:115 时间:2026-08-28 05:59:37
JSON
无输出内容。

表格明细

渠道状态延迟 msHTTPTokens输出 / 错误
DeepSeek-v4-pro-01 成功 1307 200 113
DeepSeek-v4-pro-01 成功 1373 200 113
DeepSeek-v4-pro-01 成功 1183 200 113
DeepSeek-v4-pro-03 成功 1136 200 113
DeepSeek-v4-pro-03 成功 1024 200 113
DeepSeek-v4-pro-03 成功 1066 200 113
DeepSeek-v4-pro-04 成功 1505 200 113
DeepSeek-v4-pro-04 成功 1549 200 113
DeepSeek-v4-pro-04 成功 1459 200 113
DeepSeek-v4-pro-02 成功 1778 200 113
DeepSeek-v4-pro-02 成功 1180 200 113
DeepSeek-v4-pro-02 成功 1549 200 113
jd-gemini-3.1-pro-preview 成功 2474 200 26
jd-gemini-3.1-pro-preview 成功 2309 200 26
jd-gemini-3.1-pro-preview 成功 2497 200 27
腾讯 Gemini 3.5 Flash 成功 4638 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 成功 5420 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 成功 4582 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 成功 5324 200 291 {"status":"ok","message":"stable"}
qwen3.6-plus 成功 5035 200 291 {"status":"ok","message":"stable"}
pixflow-gemini-3.1-pro-preview 失败 529 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
pixflow-gemini-3.1-pro-preview 失败 542 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
pixflow-gemini-3.1-pro-preview 失败 465 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
yuling-gpt-5.5 失败 517 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
qwen3.6-plus 成功 3681 200 192 {"status":"ok","message":"stable"}
yuling-gpt-5.5 失败 421 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
yuling-gpt-5.5 失败 522 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
Kimi K3 - Aliyun Bailian 成功 7154 200 115
Kimi K3 - Aliyun Bailian 成功 1103 200 115
Kimi K3 - Aliyun Bailian 成功 8807 200 115
Kimi K3 成功 4351 200 115 {"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply only with JSON: {\"status\":\"ok\",\""}, "logprobs": null, "finish_reason": "length"}
Kimi K3 成功 3804 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 成功 2983 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 成功 4512 200 144 {"status":"ok","message":"stable"}
Kimi K3 - TopenRouter 成功 4793 200 155 {"status":"ok","message":"stable"}
Qwen3.8-Max 成功 2134 200 147 {"status":"ok","message":"stable"}
Qwen3.8-Max 成功 1762 200 124 {"status":"ok","message":"stable"}
Qwen3.8-Max 成功 1859 200 119 {"status":"ok","message":"stable"}
MiniMax H3 Context IR 失败 240 400 - HTTP 400: binding: expr_path=content, cause=missing required parameter
MiniMax H3 Context IR 失败 199 400 - HTTP 400: binding: expr_path=content, cause=missing required parameter
MiniMax H3 Context IR 失败 194 400 - HTTP 400: binding: expr_path=content, cause=missing required parameter
yulin-gemini-3.7-flash-high 成功 5223 200 182 {"status":"ok","message":"stable"}
yulin-gemini-3.7-flash-high 成功 5689 200 169 {"status":"ok","message":"stable"}
yulin-gemini-3.7-flash-high 成功 4197 200 165 {"status":"ok","message":"stable"}
Kimi K3 - TopenRouter 成功 42998 200 115