历史详情

Run ID: 20260828-161635-8553e01b

返回历史

测试结果

Run ID: 20260828-161635-8553e01b

导出 JSON
总请求45
成功 / 失败34/11
成功率75.56%
平均延迟3154 ms
P95 / Tokens5834 / 4220
渠道模型成功失败成功率失败率稳定性平均延迟 msP95 msTokens首个错误
DeepSeek-v4-pro-03 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 771 806 339
DeepSeek-v4-pro-02 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1072 1156 339
DeepSeek-v4-pro-01 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1145 1210 339
DeepSeek-v4-pro-04 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1164 1202 339
Qwen3.8-Max qwen3.8-max 3/3 0/3 100.0% 0.0% 稳定 1831 2019 384
Kimi K3 - TopenRouter kimi-k3 3/3 0/3 100.0% 0.0% 可用 2725 5382 474
qwen3.6-plus qwen3.6-plus 3/3 0/3 100.0% 0.0% 稳定 4313 4728 724
yulin-gemini-3.7-flash-high gemini-3.7-flash-high 3/3 0/3 100.0% 0.0% 可用 4817 5219 487
腾讯 Gemini 3.5 Flash gemini-3.5-flash 3/3 0/3 100.0% 0.0% 可用 5092 5834 78
Kimi K3 kimi-k3 3/3 0/3 100.0% 0.0% 可用 5136 5570 345
Kimi K3 - Aliyun Bailian kimi/kimi-k3 3/3 0/3 100.0% 0.0% 可用 6516 8814 345
jd-gemini-3.1-pro-preview gemini-3.1-pro-preview 1/3 2/3 33.33% 66.67% 不稳定 3494 3494 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 延迟:1056 ms Tokens:113 时间:2026-08-28 16:15:07
JSON
无输出内容。
#2 DeepSeek-v4-pro-01 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1169 ms Tokens:113 时间:2026-08-28 16:15:07
JSON
无输出内容。
#3 DeepSeek-v4-pro-03 成功 HTTP 200
模型:deepseek-v4-pro 延迟:780 ms Tokens:113 时间:2026-08-28 16:15:08
JSON
无输出内容。
#4 DeepSeek-v4-pro-01 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1210 ms Tokens:113 时间:2026-08-28 16:15:08
JSON
无输出内容。
#5 DeepSeek-v4-pro-03 成功 HTTP 200
模型:deepseek-v4-pro 延迟:806 ms Tokens:113 时间:2026-08-28 16:15:09
JSON
无输出内容。
#6 DeepSeek-v4-pro-03 成功 HTTP 200
模型:deepseek-v4-pro 延迟:729 ms Tokens:113 时间:2026-08-28 16:15:10
JSON
无输出内容。
#7 DeepSeek-v4-pro-04 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1134 ms Tokens:113 时间:2026-08-28 16:15:10
JSON
无输出内容。
#8 DeepSeek-v4-pro-04 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1157 ms Tokens:113 时间:2026-08-28 16:15:10
JSON
无输出内容。
#9 DeepSeek-v4-pro-04 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1202 ms Tokens:113 时间:2026-08-28 16:15:11
JSON
无输出内容。
#10 DeepSeek-v4-pro-02 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1156 ms Tokens:113 时间:2026-08-28 16:15:11
JSON
无输出内容。
#11 DeepSeek-v4-pro-02 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1029 ms Tokens:113 时间:2026-08-28 16:15:12
JSON
无输出内容。
#12 DeepSeek-v4-pro-02 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1033 ms Tokens:113 时间:2026-08-28 16:15:13
JSON
无输出内容。
#13 jd-gemini-3.1-pro-preview 成功 HTTP 200
模型:gemini-3.1-pro-preview 延迟:3494 ms Tokens:27 时间:2026-08-28 16:15:13
JSON
无输出内容。
#14 jd-gemini-3.1-pro-preview 失败 HTTP -
模型:gemini-3.1-pro-preview 延迟:30195 ms Tokens:- 时间:2026-08-28 16:15:14
JSON
timeout: The read operation timed out
#15 jd-gemini-3.1-pro-preview 失败 HTTP -
模型:gemini-3.1-pro-preview 延迟:30217 ms Tokens:- 时间:2026-08-28 16:15:17
JSON
timeout: The read operation timed out
#16 腾讯 Gemini 3.5 Flash 成功 HTTP 200
模型:gemini-3.5-flash 延迟:5834 ms Tokens:26 时间:2026-08-28 16:15:44
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
#17 腾讯 Gemini 3.5 Flash 成功 HTTP 200
模型:gemini-3.5-flash 延迟:4912 ms Tokens:26 时间:2026-08-28 16:15:47
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 腾讯 Gemini 3.5 Flash 成功 HTTP 200
模型:gemini-3.5-flash 延迟:4531 ms Tokens:26 时间:2026-08-28 16:15:50
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 延迟:4728 ms Tokens:259 时间:2026-08-28 16:15:52
JSON
{"status":"ok","message":"stable"}
#20 qwen3.6-plus 成功 HTTP 200
模型:qwen3.6-plus 延迟:4594 ms Tokens:259 时间:2026-08-28 16:15:54
JSON
{"status":"ok","message":"stable"}
#21 pixflow-gemini-3.1-pro-preview 失败 HTTP 403
模型:gemini-3.1-pro-preview 延迟:511 ms Tokens:- 时间:2026-08-28 16:15:59
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#22 pixflow-gemini-3.1-pro-preview 失败 HTTP 403
模型:gemini-3.1-pro-preview 延迟:470 ms Tokens:- 时间:2026-08-28 16:15:59
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#23 pixflow-gemini-3.1-pro-preview 失败 HTTP 403
模型:gemini-3.1-pro-preview 延迟:523 ms Tokens:- 时间:2026-08-28 16:16:00
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#24 qwen3.6-plus 成功 HTTP 200
模型:qwen3.6-plus 延迟:3618 ms Tokens:206 时间:2026-08-28 16:15:57
JSON
{"status":"ok","message":"stable"}
#25 yuling-gpt-5.5 失败 HTTP 403
模型:gpt-5.5 延迟:501 ms Tokens:- 时间:2026-08-28 16:16:00
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#26 yuling-gpt-5.5 失败 HTTP 403
模型:gpt-5.5 延迟:545 ms Tokens:- 时间:2026-08-28 16:16:00
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#27 yuling-gpt-5.5 失败 HTTP 403
模型:gpt-5.5 延迟:459 ms Tokens:- 时间:2026-08-28 16:16:01
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#28 Kimi K3 - Aliyun Bailian 成功 HTTP 200
模型:kimi/kimi-k3 延迟:7055 ms Tokens:115 时间:2026-08-28 16:16:01
JSON
无输出内容。
#29 Kimi K3 - Aliyun Bailian 成功 HTTP 200
模型:kimi/kimi-k3 延迟:8814 ms Tokens:115 时间:2026-08-28 16:16:01
JSON
无输出内容。
#30 Kimi K3 - Aliyun Bailian 成功 HTTP 200
模型:kimi/kimi-k3 延迟:3680 ms Tokens:115 时间:2026-08-28 16:16:08
JSON
无输出内容。
#31 Kimi K3 成功 HTTP 200
模型:kimi-k3 延迟:5284 ms Tokens:115 时间:2026-08-28 16:16:10
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"}
#32 Kimi K3 成功 HTTP 200
模型:kimi-k3 延迟:4555 ms Tokens:115 时间:2026-08-28 16:16:12
JSON
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply with only JSON: {\"status"}, "logprobs": null, "finish_reason": "length"}
#33 Kimi K3 成功 HTTP 200
模型:kimi-k3 延迟:5570 ms Tokens:115 时间:2026-08-28 16:16:15
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"}
#34 Kimi K3 - TopenRouter 成功 HTTP 200
模型:kimi-k3 延迟:5382 ms Tokens:168 时间:2026-08-28 16:16:16
JSON
{"status":"ok","message":"stable"}
#35 Kimi K3 - TopenRouter 成功 HTTP 200
模型:kimi-k3 延迟:1049 ms Tokens:153 时间:2026-08-28 16:16:22
JSON
无输出内容。
#36 Kimi K3 - TopenRouter 成功 HTTP 200
模型:kimi-k3 延迟:1745 ms Tokens:153 时间:2026-08-28 16:16:21
JSON
无输出内容。
#37 Qwen3.8-Max 成功 HTTP 200
模型:qwen3.8-max 延迟:1704 ms Tokens:128 时间:2026-08-28 16:16:23
JSON
{"status":"ok","message":"stable"}
#38 Qwen3.8-Max 成功 HTTP 200
模型:qwen3.8-max 延迟:1770 ms Tokens:127 时间:2026-08-28 16:16:23
JSON
{"status":"ok","message":"stable"}
#39 MiniMax H3 Context IR 失败 HTTP 400
模型:MiniMax-H3 延迟:157 ms Tokens:- 时间:2026-08-28 16:16:24
JSON
HTTP 400: binding: expr_path=content, cause=missing required parameter
#40 MiniMax H3 Context IR 失败 HTTP 400
模型:MiniMax-H3 延迟:194 ms Tokens:- 时间:2026-08-28 16:16:25
JSON
HTTP 400: binding: expr_path=content, cause=missing required parameter
#41 MiniMax H3 Context IR 失败 HTTP 400
模型:MiniMax-H3 延迟:158 ms Tokens:- 时间:2026-08-28 16:16:25
JSON
HTTP 400: binding: expr_path=content, cause=missing required parameter
#42 Qwen3.8-Max 成功 HTTP 200
模型:qwen3.8-max 延迟:2019 ms Tokens:129 时间:2026-08-28 16:16:24
JSON
{"status":"ok","message":"stable"}
#43 yulin-gemini-3.7-flash-high 成功 HTTP 200
模型:gemini-3.7-flash-high 延迟:5219 ms Tokens:164 时间:2026-08-28 16:16:25
JSON
{"status":"ok","message":"stable"}
#44 yulin-gemini-3.7-flash-high 成功 HTTP 200
模型:gemini-3.7-flash-high 延迟:4430 ms Tokens:179 时间:2026-08-28 16:16:26
JSON
{"status":"ok","message":"stable"}
#45 yulin-gemini-3.7-flash-high 成功 HTTP 200
模型:gemini-3.7-flash-high 延迟:4802 ms Tokens:144 时间:2026-08-28 16:16:30
JSON
{"status":"ok","message":"stable"}

表格明细

渠道状态延迟 msHTTPTokens输出 / 错误
DeepSeek-v4-pro-01 成功 1056 200 113
DeepSeek-v4-pro-01 成功 1169 200 113
DeepSeek-v4-pro-03 成功 780 200 113
DeepSeek-v4-pro-01 成功 1210 200 113
DeepSeek-v4-pro-03 成功 806 200 113
DeepSeek-v4-pro-03 成功 729 200 113
DeepSeek-v4-pro-04 成功 1134 200 113
DeepSeek-v4-pro-04 成功 1157 200 113
DeepSeek-v4-pro-04 成功 1202 200 113
DeepSeek-v4-pro-02 成功 1156 200 113
DeepSeek-v4-pro-02 成功 1029 200 113
DeepSeek-v4-pro-02 成功 1033 200 113
jd-gemini-3.1-pro-preview 成功 3494 200 27
jd-gemini-3.1-pro-preview 失败 30195 - - timeout: The read operation timed out
jd-gemini-3.1-pro-preview 失败 30217 - - timeout: The read operation timed out
腾讯 Gemini 3.5 Flash 成功 5834 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 成功 4912 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 成功 4531 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 成功 4728 200 259 {"status":"ok","message":"stable"}
qwen3.6-plus 成功 4594 200 259 {"status":"ok","message":"stable"}
pixflow-gemini-3.1-pro-preview 失败 511 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
pixflow-gemini-3.1-pro-preview 失败 470 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
pixflow-gemini-3.1-pro-preview 失败 523 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
qwen3.6-plus 成功 3618 200 206 {"status":"ok","message":"stable"}
yuling-gpt-5.5 失败 501 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
yuling-gpt-5.5 失败 545 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
yuling-gpt-5.5 失败 459 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
Kimi K3 - Aliyun Bailian 成功 7055 200 115
Kimi K3 - Aliyun Bailian 成功 8814 200 115
Kimi K3 - Aliyun Bailian 成功 3680 200 115
Kimi K3 成功 5284 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 成功 4555 200 115 {"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply with only JSON: {\"status"}, "logprobs": null, "finish_reason": "length"}
Kimi K3 成功 5570 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 成功 5382 200 168 {"status":"ok","message":"stable"}
Kimi K3 - TopenRouter 成功 1049 200 153
Kimi K3 - TopenRouter 成功 1745 200 153
Qwen3.8-Max 成功 1704 200 128 {"status":"ok","message":"stable"}
Qwen3.8-Max 成功 1770 200 127 {"status":"ok","message":"stable"}
MiniMax H3 Context IR 失败 157 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
MiniMax H3 Context IR 失败 158 400 - HTTP 400: binding: expr_path=content, cause=missing required parameter
Qwen3.8-Max 成功 2019 200 129 {"status":"ok","message":"stable"}
yulin-gemini-3.7-flash-high 成功 5219 200 164 {"status":"ok","message":"stable"}
yulin-gemini-3.7-flash-high 成功 4430 200 179 {"status":"ok","message":"stable"}
yulin-gemini-3.7-flash-high 成功 4802 200 144 {"status":"ok","message":"stable"}