历史详情

Run ID: 20260829-002653-cd299df4

返回历史

测试结果

Run ID: 20260829-002653-cd299df4

导出 JSON
总请求45
成功 / 失败34/11
成功率75.56%
平均延迟3371 ms
P95 / Tokens6819 / 4755
渠道模型成功失败成功率失败率稳定性平均延迟 msP95 msTokens首个错误
DeepSeek-v4-pro-01 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 970 1237 339
DeepSeek-v4-pro-03 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1116 1206 339
DeepSeek-v4-pro-04 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1201 1284 339
DeepSeek-v4-pro-02 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1381 1602 339
Qwen3.8-Max qwen3.8-max 3/3 0/3 100.0% 0.0% 稳定 1676 1835 376
Kimi K3 - TopenRouter kimi-k3 3/3 0/3 100.0% 0.0% 可用 3559 6819 459
yulin-gemini-3.7-flash-high gemini-3.7-flash-high 3/3 0/3 100.0% 0.0% 可用 4661 5174 508
Kimi K3 kimi-k3 3/3 0/3 100.0% 0.0% 可用 4995 5485 345
Kimi K3 - Aliyun Bailian kimi/kimi-k3 3/3 0/3 100.0% 0.0% 可用 5122 6172 345
腾讯 Gemini 3.5 Flash gemini-3.5-flash 3/3 0/3 100.0% 0.0% 可用 5208 5555 78
qwen3.6-plus qwen3.6-plus 3/3 0/3 100.0% 0.0% 可用 7374 10164 1261
jd-gemini-3.1-pro-preview gemini-3.1-pro-preview 1/3 2/3 33.33% 66.67% 不稳定 2829 2829 27 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 延迟:867 ms Tokens:113 时间:2026-08-29 00:25:22
JSON
无输出内容。
#2 DeepSeek-v4-pro-01 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1237 ms Tokens:113 时间:2026-08-29 00:25:22
JSON
无输出内容。
#3 DeepSeek-v4-pro-01 成功 HTTP 200
模型:deepseek-v4-pro 延迟:808 ms Tokens:113 时间:2026-08-29 00:25:23
JSON
无输出内容。
#4 DeepSeek-v4-pro-03 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1206 ms Tokens:113 时间:2026-08-29 00:25:24
JSON
无输出内容。
#5 DeepSeek-v4-pro-03 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1161 ms Tokens:113 时间:2026-08-29 00:25:24
JSON
无输出内容。
#6 DeepSeek-v4-pro-03 成功 HTTP 200
模型:deepseek-v4-pro 延迟:981 ms Tokens:113 时间:2026-08-29 00:25:25
JSON
无输出内容。
#7 DeepSeek-v4-pro-04 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1284 ms Tokens:113 时间:2026-08-29 00:25:25
JSON
无输出内容。
#8 DeepSeek-v4-pro-04 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1164 ms Tokens:113 时间:2026-08-29 00:25:26
JSON
无输出内容。
#9 DeepSeek-v4-pro-04 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1155 ms Tokens:113 时间:2026-08-29 00:25:27
JSON
{"status":"
#10 DeepSeek-v4-pro-02 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1085 ms Tokens:113 时间:2026-08-29 00:25:27
JSON
无输出内容。
#11 DeepSeek-v4-pro-02 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1456 ms Tokens:113 时间:2026-08-29 00:25:28
JSON
无输出内容。
#12 DeepSeek-v4-pro-02 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1602 ms Tokens:113 时间:2026-08-29 00:25:28
JSON
无输出内容。
#13 jd-gemini-3.1-pro-preview 成功 HTTP 200
模型:gemini-3.1-pro-preview 延迟:2829 ms Tokens:27 时间:2026-08-29 00:25:30
JSON
无输出内容。
#14 jd-gemini-3.1-pro-preview 失败 HTTP -
模型:gemini-3.1-pro-preview 延迟:30211 ms Tokens:- 时间:2026-08-29 00:25:29
JSON
timeout: The read operation timed out
#15 jd-gemini-3.1-pro-preview 失败 HTTP -
模型:gemini-3.1-pro-preview 延迟:30144 ms Tokens:- 时间:2026-08-29 00:25:33
JSON
timeout: The read operation timed out
#16 腾讯 Gemini 3.5 Flash 成功 HTTP 200
模型:gemini-3.5-flash 延迟:4600 ms Tokens:26 时间:2026-08-29 00:25:59
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 延迟:5469 ms Tokens:26 时间:2026-08-29 00:26:03
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 延迟:5555 ms Tokens:26 时间:2026-08-29 00:26:04
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
#19 qwen3.6-plus 成功 HTTP 200
模型:qwen3.6-plus 延迟:3537 ms Tokens:202 时间:2026-08-29 00:26:10
JSON
{"status":"ok","message":"stable"}
#20 qwen3.6-plus 成功 HTTP 200
模型:qwen3.6-plus 延迟:8422 ms Tokens:466 时间:2026-08-29 00:26:08
JSON
{"status":"ok","message":"stable"}
#21 pixflow-gemini-3.1-pro-preview 失败 HTTP 403
模型:gemini-3.1-pro-preview 延迟:537 ms Tokens:- 时间:2026-08-29 00:26:17
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#22 pixflow-gemini-3.1-pro-preview 失败 HTTP 403
模型:gemini-3.1-pro-preview 延迟:529 ms Tokens:- 时间:2026-08-29 00:26:17
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#23 pixflow-gemini-3.1-pro-preview 失败 HTTP 403
模型:gemini-3.1-pro-preview 延迟:530 ms Tokens:- 时间:2026-08-29 00:26:18
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#24 yuling-gpt-5.5 失败 HTTP 403
模型:gpt-5.5 延迟:482 ms Tokens:- 时间:2026-08-29 00:26:18
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#25 yuling-gpt-5.5 失败 HTTP 403
模型:gpt-5.5 延迟:497 ms Tokens:- 时间:2026-08-29 00:26:19
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#26 yuling-gpt-5.5 失败 HTTP 403
模型:gpt-5.5 延迟:541 ms Tokens:- 时间:2026-08-29 00:26:19
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#27 qwen3.6-plus 成功 HTTP 200
模型:qwen3.6-plus 延迟:10164 ms Tokens:593 时间:2026-08-29 00:26:13
JSON
{"status":"ok","message":"stable"}
#28 Kimi K3 - Aliyun Bailian 成功 HTTP 200
模型:kimi/kimi-k3 延迟:6172 ms Tokens:115 时间:2026-08-29 00:26:20
JSON
无输出内容。
#29 Kimi K3 - Aliyun Bailian 成功 HTTP 200
模型:kimi/kimi-k3 延迟:5373 ms Tokens:115 时间:2026-08-29 00:26:23
JSON
无输出内容。
#30 Kimi K3 - Aliyun Bailian 成功 HTTP 200
模型:kimi/kimi-k3 延迟:3823 ms Tokens:115 时间:2026-08-29 00:26:26
JSON
无输出内容。
#31 Kimi K3 成功 HTTP 200
模型:kimi-k3 延迟:5485 ms Tokens:115 时间:2026-08-29 00:26:29
JSON
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply with only a JSON: {\""}, "logprobs": null, "finish_reason": "length"}
#32 Kimi K3 成功 HTTP 200
模型:kimi-k3 延迟:4825 ms Tokens:115 时间:2026-08-29 00:26:30
JSON
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply only with a specific JSON:"}, "logprobs": null, "finish_reason": "length"}
#33 Kimi K3 - TopenRouter 成功 HTTP 200
模型:kimi-k3 延迟:1624 ms Tokens:153 时间:2026-08-29 00:26:34
JSON
无输出内容。
#34 Kimi K3 - TopenRouter 成功 HTTP 200
模型:kimi-k3 延迟:2234 ms Tokens:153 时间:2026-08-29 00:26:36
JSON
无输出内容。
#35 Kimi K3 成功 HTTP 200
模型:kimi-k3 延迟:4676 ms Tokens:115 时间:2026-08-29 00:26:34
JSON
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to only reply with JSON: {\"status"}, "logprobs": null, "finish_reason": "length"}
#36 Qwen3.8-Max 成功 HTTP 200
模型:qwen3.8-max 延迟:1612 ms Tokens:125 时间:2026-08-29 00:26:39
JSON
{"status":"ok","message":"stable"}
#37 Qwen3.8-Max 成功 HTTP 200
模型:qwen3.8-max 延迟:1581 ms Tokens:125 时间:2026-08-29 00:26:40
JSON
{"status":"ok","message":"stable"}
#38 Qwen3.8-Max 成功 HTTP 200
模型:qwen3.8-max 延迟:1835 ms Tokens:126 时间:2026-08-29 00:26:42
JSON
{"status":"ok","message":"stable"}
#39 MiniMax H3 Context IR 失败 HTTP 400
模型:MiniMax-H3 延迟:215 ms Tokens:- 时间:2026-08-29 00:26:44
JSON
HTTP 400: binding: expr_path=content, cause=missing required parameter
#40 MiniMax H3 Context IR 失败 HTTP 400
模型:MiniMax-H3 延迟:174 ms Tokens:- 时间:2026-08-29 00:26:44
JSON
HTTP 400: binding: expr_path=content, cause=missing required parameter
#41 MiniMax H3 Context IR 失败 HTTP 400
模型:MiniMax-H3 延迟:236 ms Tokens:- 时间:2026-08-29 00:26:44
JSON
HTTP 400: binding: expr_path=content, cause=missing required parameter
#42 Kimi K3 - TopenRouter 成功 HTTP 200
模型:kimi-k3 延迟:6819 ms Tokens:153 时间:2026-08-29 00:26:38
JSON
无输出内容。
#43 yulin-gemini-3.7-flash-high 成功 HTTP 200
模型:gemini-3.7-flash-high 延迟:5174 ms Tokens:174 时间:2026-08-29 00:26:44
JSON
{"status":"ok","message":"stable"}
#44 yulin-gemini-3.7-flash-high 成功 HTTP 200
模型:gemini-3.7-flash-high 延迟:4910 ms Tokens:170 时间:2026-08-29 00:26:45
JSON
{"status":"ok","message":"stable"}
#45 yulin-gemini-3.7-flash-high 成功 HTTP 200
模型:gemini-3.7-flash-high 延迟:3901 ms Tokens:164 时间:2026-08-29 00:26:50
JSON
{"status":"ok","message":"stable"}

表格明细

渠道状态延迟 msHTTPTokens输出 / 错误
DeepSeek-v4-pro-01 成功 867 200 113
DeepSeek-v4-pro-01 成功 1237 200 113
DeepSeek-v4-pro-01 成功 808 200 113
DeepSeek-v4-pro-03 成功 1206 200 113
DeepSeek-v4-pro-03 成功 1161 200 113
DeepSeek-v4-pro-03 成功 981 200 113
DeepSeek-v4-pro-04 成功 1284 200 113
DeepSeek-v4-pro-04 成功 1164 200 113
DeepSeek-v4-pro-04 成功 1155 200 113 {"status":"
DeepSeek-v4-pro-02 成功 1085 200 113
DeepSeek-v4-pro-02 成功 1456 200 113
DeepSeek-v4-pro-02 成功 1602 200 113
jd-gemini-3.1-pro-preview 成功 2829 200 27
jd-gemini-3.1-pro-preview 失败 30211 - - timeout: The read operation timed out
jd-gemini-3.1-pro-preview 失败 30144 - - timeout: The read operation timed out
腾讯 Gemini 3.5 Flash 成功 4600 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 成功 5469 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 成功 5555 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
qwen3.6-plus 成功 3537 200 202 {"status":"ok","message":"stable"}
qwen3.6-plus 成功 8422 200 466 {"status":"ok","message":"stable"}
pixflow-gemini-3.1-pro-preview 失败 537 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
pixflow-gemini-3.1-pro-preview 失败 529 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
pixflow-gemini-3.1-pro-preview 失败 530 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
yuling-gpt-5.5 失败 482 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
yuling-gpt-5.5 失败 497 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
yuling-gpt-5.5 失败 541 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
qwen3.6-plus 成功 10164 200 593 {"status":"ok","message":"stable"}
Kimi K3 - Aliyun Bailian 成功 6172 200 115
Kimi K3 - Aliyun Bailian 成功 5373 200 115
Kimi K3 - Aliyun Bailian 成功 3823 200 115
Kimi K3 成功 5485 200 115 {"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply with only a JSON: {\""}, "logprobs": null, "finish_reason": "length"}
Kimi K3 成功 4825 200 115 {"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply only with a specific JSON:"}, "logprobs": null, "finish_reason": "length"}
Kimi K3 - TopenRouter 成功 1624 200 153
Kimi K3 - TopenRouter 成功 2234 200 153
Kimi K3 成功 4676 200 115 {"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to only reply with JSON: {\"status"}, "logprobs": null, "finish_reason": "length"}
Qwen3.8-Max 成功 1612 200 125 {"status":"ok","message":"stable"}
Qwen3.8-Max 成功 1581 200 125 {"status":"ok","message":"stable"}
Qwen3.8-Max 成功 1835 200 126 {"status":"ok","message":"stable"}
MiniMax H3 Context IR 失败 215 400 - HTTP 400: binding: expr_path=content, cause=missing required parameter
MiniMax H3 Context IR 失败 174 400 - HTTP 400: binding: expr_path=content, cause=missing required parameter
MiniMax H3 Context IR 失败 236 400 - HTTP 400: binding: expr_path=content, cause=missing required parameter
Kimi K3 - TopenRouter 成功 6819 200 153
yulin-gemini-3.7-flash-high 成功 5174 200 174 {"status":"ok","message":"stable"}
yulin-gemini-3.7-flash-high 成功 4910 200 170 {"status":"ok","message":"stable"}
yulin-gemini-3.7-flash-high 成功 3901 200 164 {"status":"ok","message":"stable"}