历史详情

Run ID: 20260828-090435-4c8bf72e

返回历史

测试结果

Run ID: 20260828-090435-4c8bf72e

导出 JSON
总请求45
成功 / 失败36/9
成功率80.0%
平均延迟2750 ms
P95 / Tokens4931 / 4266
渠道模型成功失败成功率失败率稳定性平均延迟 msP95 msTokens首个错误
DeepSeek-v4-pro-04 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1116 1247 339
DeepSeek-v4-pro-02 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1226 1318 339
DeepSeek-v4-pro-01 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1250 1472 339
DeepSeek-v4-pro-03 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1389 1559 339
Qwen3.8-Max qwen3.8-max 3/3 0/3 100.0% 0.0% 稳定 1919 1987 384
jd-gemini-3.1-pro-preview gemini-3.1-pro-preview 3/3 0/3 100.0% 0.0% 稳定 2504 2900 78
Kimi K3 - Aliyun Bailian kimi/kimi-k3 3/3 0/3 100.0% 0.0% 稳定 2536 2854 345
Kimi K3 - TopenRouter kimi-k3 3/3 0/3 100.0% 0.0% 稳定 2698 3500 396
Kimi K3 kimi-k3 3/3 0/3 100.0% 0.0% 稳定 3882 4620 345
yulin-gemini-3.7-flash-high gemini-3.7-flash-high 3/3 0/3 100.0% 0.0% 稳定 4641 4931 491
qwen3.6-plus qwen3.6-plus 3/3 0/3 100.0% 0.0% 可用 4880 5974 793
腾讯 Gemini 3.5 Flash gemini-3.5-flash 3/3 0/3 100.0% 0.0% 可用 4954 5646 78
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 延迟:1249 ms Tokens:113 时间:2026-08-28 09:03:42
JSON
无输出内容。
#2 DeepSeek-v4-pro-01 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1472 ms Tokens:113 时间:2026-08-28 09:03:42
JSON
无输出内容。
#3 DeepSeek-v4-pro-01 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1030 ms Tokens:113 时间:2026-08-28 09:03:43
JSON
无输出内容。
#4 DeepSeek-v4-pro-03 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1446 ms Tokens:113 时间:2026-08-28 09:03:43
JSON
无输出内容。
#5 DeepSeek-v4-pro-03 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1163 ms Tokens:113 时间:2026-08-28 09:03:44
JSON
无输出内容。
#6 DeepSeek-v4-pro-04 成功 HTTP 200
模型:deepseek-v4-pro 延迟:901 ms Tokens:113 时间:2026-08-28 09:03:45
JSON
无输出内容。
#7 DeepSeek-v4-pro-03 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1559 ms Tokens:113 时间:2026-08-28 09:03:45
JSON
无输出内容。
#8 DeepSeek-v4-pro-04 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1202 ms Tokens:113 时间:2026-08-28 09:03:46
JSON
无输出内容。
#9 DeepSeek-v4-pro-04 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1247 ms Tokens:113 时间:2026-08-28 09:03:46
JSON
无输出内容。
#10 DeepSeek-v4-pro-02 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1094 ms Tokens:113 时间:2026-08-28 09:03:47
JSON
无输出内容。
#11 DeepSeek-v4-pro-02 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1268 ms Tokens:113 时间:2026-08-28 09:03:48
JSON
无输出内容。
#12 DeepSeek-v4-pro-02 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1318 ms Tokens:113 时间:2026-08-28 09:03:49
JSON
无输出内容。
#13 jd-gemini-3.1-pro-preview 成功 HTTP 200
模型:gemini-3.1-pro-preview 延迟:2227 ms Tokens:26 时间:2026-08-28 09:03:49
JSON
无输出内容。
#14 jd-gemini-3.1-pro-preview 成功 HTTP 200
模型:gemini-3.1-pro-preview 延迟:2387 ms Tokens:26 时间:2026-08-28 09:03:50
JSON
无输出内容。
#15 jd-gemini-3.1-pro-preview 成功 HTTP 200
模型:gemini-3.1-pro-preview 延迟:2900 ms Tokens:26 时间:2026-08-28 09:03:51
JSON
无输出内容。
#16 腾讯 Gemini 3.5 Flash 成功 HTTP 200
模型:gemini-3.5-flash 延迟:5646 ms Tokens:26 时间:2026-08-28 09:03:52
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 延迟:4683 ms Tokens:26 时间:2026-08-28 09:03:54
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 延迟:4534 ms Tokens:26 时间:2026-08-28 09:03:58
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 延迟:4583 ms Tokens:221 时间:2026-08-28 09:03:59
JSON
{"status":"ok","message":"stable"}
#20 qwen3.6-plus 成功 HTTP 200
模型:qwen3.6-plus 延迟:4084 ms Tokens:226 时间:2026-08-28 09:04:02
JSON
{"status":"ok","message":"stable"}
#21 pixflow-gemini-3.1-pro-preview 失败 HTTP 403
模型:gemini-3.1-pro-preview 延迟:520 ms Tokens:- 时间:2026-08-28 09:04:07
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#22 pixflow-gemini-3.1-pro-preview 失败 HTTP 403
模型:gemini-3.1-pro-preview 延迟:474 ms Tokens:- 时间:2026-08-28 09:04:07
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#23 pixflow-gemini-3.1-pro-preview 失败 HTTP 403
模型:gemini-3.1-pro-preview 延迟:515 ms Tokens:- 时间:2026-08-28 09:04:08
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#24 yuling-gpt-5.5 失败 HTTP 403
模型:gpt-5.5 延迟:583 ms Tokens:- 时间:2026-08-28 09:04:08
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#25 yuling-gpt-5.5 失败 HTTP 403
模型:gpt-5.5 延迟:463 ms Tokens:- 时间:2026-08-28 09:04:09
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#26 qwen3.6-plus 成功 HTTP 200
模型:qwen3.6-plus 延迟:5974 ms Tokens:346 时间:2026-08-28 09:04:03
JSON
{"status":"ok","message":"stable"}
#27 yuling-gpt-5.5 失败 HTTP 403
模型:gpt-5.5 延迟:551 ms Tokens:- 时间:2026-08-28 09:04:09
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#28 Kimi K3 - Aliyun Bailian 成功 HTTP 200
模型:kimi/kimi-k3 延迟:2101 ms Tokens:115 时间:2026-08-28 09:04:10
JSON
无输出内容。
#29 Kimi K3 - Aliyun Bailian 成功 HTTP 200
模型:kimi/kimi-k3 延迟:2653 ms Tokens:115 时间:2026-08-28 09:04:09
JSON
无输出内容。
#30 Kimi K3 - Aliyun Bailian 成功 HTTP 200
模型:kimi/kimi-k3 延迟:2854 ms Tokens:115 时间:2026-08-28 09:04:12
JSON
无输出内容。
#31 Kimi K3 成功 HTTP 200
模型:kimi-k3 延迟:4001 ms Tokens:115 时间:2026-08-28 09:04:12
JSON
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to only reply with a specific JSON: {\"status\":\""}, "logprobs": null, "finish_reason": "length"}
#32 Kimi K3 成功 HTTP 200
模型:kimi-k3 延迟:3026 ms Tokens:115 时间:2026-08-28 09:04:16
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 延迟:4620 ms Tokens:115 时间:2026-08-28 09:04:15
JSON
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to only reply with JSON: {\"status\":\"ok\",\""}, "logprobs": null, "finish_reason": "length"}
#34 Kimi K3 - TopenRouter 成功 HTTP 200
模型:kimi-k3 延迟:1287 ms Tokens:115 时间:2026-08-28 09:04:19
JSON
无输出内容。
#35 Kimi K3 - TopenRouter 成功 HTTP 200
模型:kimi-k3 延迟:3500 ms Tokens:116 时间:2026-08-28 09:04:19
JSON
无输出内容。
#36 Kimi K3 - TopenRouter 成功 HTTP 200
模型:kimi-k3 延迟:3309 ms Tokens:165 时间:2026-08-28 09:04:21
JSON
{"status":"ok","message":"stable"}
#37 Qwen3.8-Max 成功 HTTP 200
模型:qwen3.8-max 延迟:1951 ms Tokens:131 时间:2026-08-28 09:04:22
JSON
{"status":"ok","message":"stable"}
#38 Qwen3.8-Max 成功 HTTP 200
模型:qwen3.8-max 延迟:1987 ms Tokens:129 时间:2026-08-28 09:04:24
JSON
{"status":"ok","message":"stable"}
#39 MiniMax H3 Context IR 失败 HTTP 400
模型:MiniMax-H3 延迟:194 ms Tokens:- 时间:2026-08-28 09:04:26
JSON
HTTP 400: binding: expr_path=content, cause=missing required parameter
#40 MiniMax H3 Context IR 失败 HTTP 400
模型:MiniMax-H3 延迟:157 ms Tokens:- 时间:2026-08-28 09:04:26
JSON
HTTP 400: binding: expr_path=content, cause=missing required parameter
#41 Qwen3.8-Max 成功 HTTP 200
模型:qwen3.8-max 延迟:1821 ms Tokens:124 时间:2026-08-28 09:04:24
JSON
{"status":"ok","message":"stable"}
#42 MiniMax H3 Context IR 失败 HTTP 400
模型:MiniMax-H3 延迟:187 ms Tokens:- 时间:2026-08-28 09:04:26
JSON
HTTP 400: binding: expr_path=content, cause=missing required parameter
#43 yulin-gemini-3.7-flash-high 成功 HTTP 200
模型:gemini-3.7-flash-high 延迟:4885 ms Tokens:150 时间:2026-08-28 09:04:26
JSON
{"status":"ok","message":"stable"}
#44 yulin-gemini-3.7-flash-high 成功 HTTP 200
模型:gemini-3.7-flash-high 延迟:4931 ms Tokens:173 时间:2026-08-28 09:04:26
JSON
{"status":"ok","message":"stable"}
#45 yulin-gemini-3.7-flash-high 成功 HTTP 200
模型:gemini-3.7-flash-high 延迟:4107 ms Tokens:168 时间:2026-08-28 09:04:31
JSON
{"status":"ok","message":"stable"}

表格明细

渠道状态延迟 msHTTPTokens输出 / 错误
DeepSeek-v4-pro-01 成功 1249 200 113
DeepSeek-v4-pro-01 成功 1472 200 113
DeepSeek-v4-pro-01 成功 1030 200 113
DeepSeek-v4-pro-03 成功 1446 200 113
DeepSeek-v4-pro-03 成功 1163 200 113
DeepSeek-v4-pro-04 成功 901 200 113
DeepSeek-v4-pro-03 成功 1559 200 113
DeepSeek-v4-pro-04 成功 1202 200 113
DeepSeek-v4-pro-04 成功 1247 200 113
DeepSeek-v4-pro-02 成功 1094 200 113
DeepSeek-v4-pro-02 成功 1268 200 113
DeepSeek-v4-pro-02 成功 1318 200 113
jd-gemini-3.1-pro-preview 成功 2227 200 26
jd-gemini-3.1-pro-preview 成功 2387 200 26
jd-gemini-3.1-pro-preview 成功 2900 200 26
腾讯 Gemini 3.5 Flash 成功 5646 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 成功 4683 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 成功 4534 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 成功 4583 200 221 {"status":"ok","message":"stable"}
qwen3.6-plus 成功 4084 200 226 {"status":"ok","message":"stable"}
pixflow-gemini-3.1-pro-preview 失败 520 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
pixflow-gemini-3.1-pro-preview 失败 474 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
pixflow-gemini-3.1-pro-preview 失败 515 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
yuling-gpt-5.5 失败 583 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"}
qwen3.6-plus 成功 5974 200 346 {"status":"ok","message":"stable"}
yuling-gpt-5.5 失败 551 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
Kimi K3 - Aliyun Bailian 成功 2101 200 115
Kimi K3 - Aliyun Bailian 成功 2653 200 115
Kimi K3 - Aliyun Bailian 成功 2854 200 115
Kimi K3 成功 4001 200 115 {"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to only reply with a specific JSON: {\"status\":\""}, "logprobs": null, "finish_reason": "length"}
Kimi K3 成功 3026 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 成功 4620 200 115 {"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to only reply with JSON: {\"status\":\"ok\",\""}, "logprobs": null, "finish_reason": "length"}
Kimi K3 - TopenRouter 成功 1287 200 115
Kimi K3 - TopenRouter 成功 3500 200 116
Kimi K3 - TopenRouter 成功 3309 200 165 {"status":"ok","message":"stable"}
Qwen3.8-Max 成功 1951 200 131 {"status":"ok","message":"stable"}
Qwen3.8-Max 成功 1987 200 129 {"status":"ok","message":"stable"}
MiniMax H3 Context IR 失败 194 400 - HTTP 400: binding: expr_path=content, cause=missing required parameter
MiniMax H3 Context IR 失败 157 400 - HTTP 400: binding: expr_path=content, cause=missing required parameter
Qwen3.8-Max 成功 1821 200 124 {"status":"ok","message":"stable"}
MiniMax H3 Context IR 失败 187 400 - HTTP 400: binding: expr_path=content, cause=missing required parameter
yulin-gemini-3.7-flash-high 成功 4885 200 150 {"status":"ok","message":"stable"}
yulin-gemini-3.7-flash-high 成功 4931 200 173 {"status":"ok","message":"stable"}
yulin-gemini-3.7-flash-high 成功 4107 200 168 {"status":"ok","message":"stable"}