历史详情

Run ID: 20260830-005152-f38eded7

返回历史

测试结果

Run ID: 20260830-005152-f38eded7

导出 JSON
总请求45
成功 / 失败36/9
成功率80.0%
平均延迟3519 ms
P95 / Tokens7477 / 4955
渠道模型成功失败成功率失败率稳定性平均延迟 msP95 msTokens首个错误
DeepSeek-v4-pro-04 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 969 1177 339
DeepSeek-v4-pro-02 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 979 1076 339
DeepSeek-v4-pro-01 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1054 1223 339
DeepSeek-v4-pro-03 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1099 1153 339
Kimi K3 - Aliyun Bailian kimi/kimi-k3 3/3 0/3 100.0% 0.0% 稳定 2448 2669 345
Qwen3.8-Max qwen3.8-max 3/3 0/3 100.0% 0.0% 稳定 2869 3072 409
Kimi K3 - TopenRouter kimi-k3 3/3 0/3 100.0% 0.0% 稳定 3215 4056 632
腾讯 Gemini 3.5 Flash gemini-3.5-flash 3/3 0/3 100.0% 0.0% 可用 5275 5910 78
Kimi K3 kimi-k3 3/3 0/3 100.0% 0.0% 可用 5392 6479 345
jd-gemini-3.1-pro-preview gemini-3.1-pro-preview 3/3 0/3 100.0% 0.0% 可用 5588 11594 80
yulin-gemini-3.7-flash-high gemini-3.7-flash-high 3/3 0/3 100.0% 0.0% 可用 6025 7477 483
qwen3.6-plus qwen3.6-plus 3/3 0/3 100.0% 0.0% 可用 7314 10805 1227
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 延迟:1201 ms Tokens:113 时间:2026-08-30 00:50:44
JSON
无输出内容。
#2 DeepSeek-v4-pro-01 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1223 ms Tokens:113 时间:2026-08-30 00:50:44
JSON
无输出内容。
#3 DeepSeek-v4-pro-01 成功 HTTP 200
模型:deepseek-v4-pro 延迟:740 ms Tokens:113 时间:2026-08-30 00:50:46
JSON
无输出内容。
#4 DeepSeek-v4-pro-03 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1153 ms Tokens:113 时间:2026-08-30 00:50:46
JSON
无输出内容。
#5 DeepSeek-v4-pro-03 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1025 ms Tokens:113 时间:2026-08-30 00:50:46
JSON
无输出内容。
#6 DeepSeek-v4-pro-03 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1120 ms Tokens:113 时间:2026-08-30 00:50:47
JSON
无输出内容。
#7 DeepSeek-v4-pro-04 成功 HTTP 200
模型:deepseek-v4-pro 延迟:859 ms Tokens:113 时间:2026-08-30 00:50:47
JSON
无输出内容。
#8 DeepSeek-v4-pro-04 成功 HTTP 200
模型:deepseek-v4-pro 延迟:873 ms Tokens:113 时间:2026-08-30 00:50:48
JSON
无输出内容。
#9 DeepSeek-v4-pro-04 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1177 ms Tokens:113 时间:2026-08-30 00:50:48
JSON
{"status":"
#10 DeepSeek-v4-pro-02 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1051 ms Tokens:113 时间:2026-08-30 00:50:49
JSON
无输出内容。
#11 DeepSeek-v4-pro-02 成功 HTTP 200
模型:deepseek-v4-pro 延迟:812 ms Tokens:113 时间:2026-08-30 00:50:49
JSON
无输出内容。
#12 DeepSeek-v4-pro-02 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1076 ms Tokens:113 时间:2026-08-30 00:50:50
JSON
无输出内容。
#13 jd-gemini-3.1-pro-preview 成功 HTTP 200
模型:gemini-3.1-pro-preview 延迟:2002 ms Tokens:26 时间:2026-08-30 00:50:51
JSON
无输出内容。
#14 jd-gemini-3.1-pro-preview 成功 HTTP 200
模型:gemini-3.1-pro-preview 延迟:3170 ms Tokens:27 时间:2026-08-30 00:50:53
JSON
无输出内容。
#15 腾讯 Gemini 3.5 Flash 成功 HTTP 200
模型:gemini-3.5-flash 延迟:4408 ms Tokens:26 时间:2026-08-30 00:50:56
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
#16 jd-gemini-3.1-pro-preview 成功 HTTP 200
模型:gemini-3.1-pro-preview 延迟:11594 ms Tokens:27 时间:2026-08-30 00:50:50
JSON
无输出内容。
#17 腾讯 Gemini 3.5 Flash 成功 HTTP 200
模型:gemini-3.5-flash 延迟:5910 ms Tokens:26 时间:2026-08-30 00:51:00
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 延迟:5509 ms Tokens:26 时间:2026-08-30 00:51:02
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 延迟:4799 ms Tokens:258 时间:2026-08-30 00:51:07
JSON
{"status":"ok","message":"stable"}
#20 qwen3.6-plus 成功 HTTP 200
模型:qwen3.6-plus 延迟:10805 ms Tokens:617 时间:2026-08-30 00:51:06
JSON
{"status":"ok","message":"stable"}
#21 pixflow-gemini-3.1-pro-preview 失败 HTTP 403
模型:gemini-3.1-pro-preview 延迟:540 ms Tokens:- 时间:2026-08-30 00:51: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 延迟:502 ms Tokens:- 时间:2026-08-30 00:51:18
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#23 qwen3.6-plus 成功 HTTP 200
模型:qwen3.6-plus 延迟:6340 ms Tokens:352 时间:2026-08-30 00:51:12
JSON
{"status":"ok","message":"stable"}
#24 pixflow-gemini-3.1-pro-preview 失败 HTTP 403
模型:gemini-3.1-pro-preview 延迟:531 ms Tokens:- 时间:2026-08-30 00:51:18
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#25 yuling-gpt-5.5 失败 HTTP 403
模型:gpt-5.5 延迟:529 ms Tokens:- 时间:2026-08-30 00:51:18
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#26 yuling-gpt-5.5 失败 HTTP 403
模型:gpt-5.5 延迟:449 ms Tokens:- 时间:2026-08-30 00:51:19
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#27 yuling-gpt-5.5 失败 HTTP 403
模型:gpt-5.5 延迟:463 ms Tokens:- 时间:2026-08-30 00:51:19
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#28 Kimi K3 - Aliyun Bailian 成功 HTTP 200
模型:kimi/kimi-k3 延迟:2461 ms Tokens:115 时间:2026-08-30 00:51:19
JSON
无输出内容。
#29 Kimi K3 - Aliyun Bailian 成功 HTTP 200
模型:kimi/kimi-k3 延迟:2669 ms Tokens:115 时间:2026-08-30 00:51:19
JSON
无输出内容。
#30 Kimi K3 - Aliyun Bailian 成功 HTTP 200
模型:kimi/kimi-k3 延迟:2215 ms Tokens:115 时间:2026-08-30 00:51:22
JSON
无输出内容。
#31 Kimi K3 成功 HTTP 200
模型:kimi-k3 延迟:4336 ms Tokens:115 时间:2026-08-30 00:51:24
JSON
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to respond only with JSON: {\"status"}, "logprobs": null, "finish_reason": "length"}
#32 Kimi K3 成功 HTTP 200
模型:kimi-k3 延迟:6479 ms Tokens:115 时间:2026-08-30 00:51:22
JSON
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply with only a specific JSON:"}, "logprobs": null, "finish_reason": "length"}
#33 Kimi K3 - TopenRouter 成功 HTTP 200
模型:kimi-k3 延迟:2662 ms Tokens:196 时间:2026-08-30 00:51:29
JSON
{"status":"ok","message":"stable"}
#34 Kimi K3 成功 HTTP 200
模型:kimi-k3 延迟:5361 ms Tokens:115 时间:2026-08-30 00:51:28
JSON
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply only with JSON: {\"status"}, "logprobs": null, "finish_reason": "length"}
#35 Kimi K3 - TopenRouter 成功 HTTP 200
模型:kimi-k3 延迟:4056 ms Tokens:236 时间:2026-08-30 00:51:31
JSON
{"status":"ok","message":"stable"}
#36 Kimi K3 - TopenRouter 成功 HTTP 200
模型:kimi-k3 延迟:2928 ms Tokens:200 时间:2026-08-30 00:51:34
JSON
{"status":"ok","message":"stable"}
#37 Qwen3.8-Max 成功 HTTP 200
模型:qwen3.8-max 延迟:2983 ms Tokens:134 时间:2026-08-30 00:51:35
JSON
{"status":"ok","message":"stable"}
#38 Qwen3.8-Max 成功 HTTP 200
模型:qwen3.8-max 延迟:2553 ms Tokens:141 时间:2026-08-30 00:51:37
JSON
{"status":"ok","message":"stable"}
#39 MiniMax H3 Context IR 失败 HTTP 400
模型:MiniMax-H3 延迟:240 ms Tokens:- 时间:2026-08-30 00:51:39
JSON
HTTP 400: binding: expr_path=content, cause=missing required parameter
#40 MiniMax H3 Context IR 失败 HTTP 400
模型:MiniMax-H3 延迟:173 ms Tokens:- 时间:2026-08-30 00:51:39
JSON
HTTP 400: binding: expr_path=content, cause=missing required parameter
#41 MiniMax H3 Context IR 失败 HTTP 400
模型:MiniMax-H3 延迟:176 ms Tokens:- 时间:2026-08-30 00:51:39
JSON
HTTP 400: binding: expr_path=content, cause=missing required parameter
#42 Qwen3.8-Max 成功 HTTP 200
模型:qwen3.8-max 延迟:3072 ms Tokens:134 时间:2026-08-30 00:51:38
JSON
{"status":"ok","message":"stable"}
#43 yulin-gemini-3.7-flash-high 成功 HTTP 200
模型:gemini-3.7-flash-high 延迟:4812 ms Tokens:146 时间:2026-08-30 00:51:40
JSON
{"status":"ok","message":"stable"}
#44 yulin-gemini-3.7-flash-high 成功 HTTP 200
模型:gemini-3.7-flash-high 延迟:5787 ms Tokens:165 时间:2026-08-30 00:51:41
JSON
{"status":"ok","message":"stable"}
#45 yulin-gemini-3.7-flash-high 成功 HTTP 200
模型:gemini-3.7-flash-high 延迟:7477 ms Tokens:172 时间:2026-08-30 00:51:44
JSON
{"status":"ok","message":"stable"}

表格明细

渠道状态延迟 msHTTPTokens输出 / 错误
DeepSeek-v4-pro-01 成功 1201 200 113
DeepSeek-v4-pro-01 成功 1223 200 113
DeepSeek-v4-pro-01 成功 740 200 113
DeepSeek-v4-pro-03 成功 1153 200 113
DeepSeek-v4-pro-03 成功 1025 200 113
DeepSeek-v4-pro-03 成功 1120 200 113
DeepSeek-v4-pro-04 成功 859 200 113
DeepSeek-v4-pro-04 成功 873 200 113
DeepSeek-v4-pro-04 成功 1177 200 113 {"status":"
DeepSeek-v4-pro-02 成功 1051 200 113
DeepSeek-v4-pro-02 成功 812 200 113
DeepSeek-v4-pro-02 成功 1076 200 113
jd-gemini-3.1-pro-preview 成功 2002 200 26
jd-gemini-3.1-pro-preview 成功 3170 200 27
腾讯 Gemini 3.5 Flash 成功 4408 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
jd-gemini-3.1-pro-preview 成功 11594 200 27
腾讯 Gemini 3.5 Flash 成功 5910 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 成功 5509 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 成功 4799 200 258 {"status":"ok","message":"stable"}
qwen3.6-plus 成功 10805 200 617 {"status":"ok","message":"stable"}
pixflow-gemini-3.1-pro-preview 失败 540 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
pixflow-gemini-3.1-pro-preview 失败 502 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
qwen3.6-plus 成功 6340 200 352 {"status":"ok","message":"stable"}
pixflow-gemini-3.1-pro-preview 失败 531 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
yuling-gpt-5.5 失败 529 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
yuling-gpt-5.5 失败 449 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
yuling-gpt-5.5 失败 463 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
Kimi K3 - Aliyun Bailian 成功 2461 200 115
Kimi K3 - Aliyun Bailian 成功 2669 200 115
Kimi K3 - Aliyun Bailian 成功 2215 200 115
Kimi K3 成功 4336 200 115 {"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to respond only with JSON: {\"status"}, "logprobs": null, "finish_reason": "length"}
Kimi K3 成功 6479 200 115 {"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply with only a specific JSON:"}, "logprobs": null, "finish_reason": "length"}
Kimi K3 - TopenRouter 成功 2662 200 196 {"status":"ok","message":"stable"}
Kimi K3 成功 5361 200 115 {"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply only with JSON: {\"status"}, "logprobs": null, "finish_reason": "length"}
Kimi K3 - TopenRouter 成功 4056 200 236 {"status":"ok","message":"stable"}
Kimi K3 - TopenRouter 成功 2928 200 200 {"status":"ok","message":"stable"}
Qwen3.8-Max 成功 2983 200 134 {"status":"ok","message":"stable"}
Qwen3.8-Max 成功 2553 200 141 {"status":"ok","message":"stable"}
MiniMax H3 Context IR 失败 240 400 - HTTP 400: binding: expr_path=content, cause=missing required parameter
MiniMax H3 Context IR 失败 173 400 - HTTP 400: binding: expr_path=content, cause=missing required parameter
MiniMax H3 Context IR 失败 176 400 - HTTP 400: binding: expr_path=content, cause=missing required parameter
Qwen3.8-Max 成功 3072 200 134 {"status":"ok","message":"stable"}
yulin-gemini-3.7-flash-high 成功 4812 200 146 {"status":"ok","message":"stable"}
yulin-gemini-3.7-flash-high 成功 5787 200 165 {"status":"ok","message":"stable"}
yulin-gemini-3.7-flash-high 成功 7477 200 172 {"status":"ok","message":"stable"}