Interview Bank

Build an AI Short-Drama Production Pipeline With Agents in 14 Days

D1 What an AI Short-Drama Production Pipeline Looks Like: Breaking Down the Stages, a Task-Graph Architecture, and Choosing Among Four Categories of Generation Models

• Why wrap a vendor SDK in your own provider interface, and when does that layer become a liability?为什么要在厂商 SDK 之上再套一层自己的 provider 接口？什么时候这层反而是负担？

  Common in ChinaCommon overseasBasic#provider-abstraction#architecture

  How to reason about it · think before answering

  1. The screen is whether you have ever actually swapped a vendor. Answering only decoupling and easy replacement is what everyone says; the signal is naming what the layer buys and what it costs.
  2. How to break it down: ask what you lose without the layer. Three concrete things — offline runnability (you can only stub when network egress is funneled into one place), multi-vendor coexistence (business code expresses an action, not one vendor's four-step flow), and metering (every call's cost must be recorded in exactly one place).
  3. Then place the abstraction: define it by business action, not by the vendor's HTTP request. Submit, poll, retrieve, download for an async video job is one generate to the caller; leaking those four steps upward defeats the purpose.
  4. Conclusion and cost: the layer sands off vendor-specific capabilities, such as first-and-last-frame conditioning or structured camera parameters. The fix is not a wider interface but one optional passthrough field, so the single call site explicitly admits it is vendor-bound.
  5. When it is a liability: single vendor forever and no offline path. Two warning signs — adding a vendor forced a signature change across the other implementations, or a vendor-only parameter name appeared in the interface. Both mean you abstracted the least common multiple of vendor features.
  6. Likely follow-up: why not just use an aggregation gateway or SDK? You still need your own interface, because aggregators normalize protocols but not your on-disk artifact contract or your cost ledger.

  分析过程 · 先想清楚再作答

  1. 这题在筛「有没有真的换过一次厂商」。只答「解耦、方便替换」的人，说的是一句所有人都会说的话，区分度在于你能不能给出「这层带来了什么、又赔上了什么」的具体清单。
  2. 怎么拆：先问自己「如果不套这层，哪些能力会散掉」。答案有三样，而且都能落到具体文件上——离线可跑（网络出口收敛到一处才可能打桩）、多厂商并存（业务代码写的是动作而不是某家的四步流程）、计量收口（每次调用的花费必须有唯一一处记账）。
  3. 接着说抽象的位置：接口要按业务动作定义，不按厂商的 HTTP 请求定义。异步视频任务的提交、轮询、取件、下载四步，对业务代码来说是一个 generate；把这四步漏到业务层，抽象就白做了。
  4. 结论与代价：这层会磨掉各家的独有能力（某家支持首尾帧、某家支持结构化运镜参数）。正确处理不是把接口撑大，而是留一个可选透传字段，让需要它的那一处显式承认自己绑定了某一家。
  5. 什么时候是负担：你只会用一家、也永远不会离线跑的时候；以及出现两个信号时——为加一个厂商改了接口签名让另外三个实现跟着改，或者接口里出现了只有一家有的参数名。这两个信号说明抽象抽在了厂商能力的最小公倍数上，位置错了。
  6. 可预期的追问：那要不要直接用某个统一网关或聚合 SDK？可以，但你仍然需要自己的接口，因为聚合层解决的是协议差异，解决不了你自己的落盘契约与记账口径。

  Key points

  • Name three concrete reasons: offline runnability, multi-vendor coexistence, and a single metering point
  • Define the interface by business action; submit-poll-retrieve-download stays inside the implementation
  • Put the output file path in the contract, because vendor image and video URLs are short-lived temporary links
  • The cost is losing vendor-specific features; handle it with one optional passthrough field, not a fatter interface
  • Two signs you abstracted wrong: adding a vendor changes the signature, or a vendor-only parameter leaks into the interface

  答题要点

  • 三个理由要说具体：离线可跑、多厂商并存、计量收口，每一个都对应一处真实代码
  • 接口按业务动作定义，异步任务的提交轮询取件下载四步必须关在实现里
  • 把落盘路径写进接口契约，因为厂商返回的图片与视频链接都是会失效的临时链接
  • 代价是磨掉独有能力，用可选透传字段处理，而不是撑大公共接口
  • 两个「抽错了」的信号：加厂商要改签名、接口里出现厂商专有参数名

D2 The Script Agent: Turning a Single Sentence Into Structured Data — Character Cards, Scenes, and Shots

• How do you get a model to emit valid structured data reliably, and what do you do when schema validation fails?怎么让模型稳定输出合法的结构化数据？schema 校验失败时你会怎么处理？

  Common in ChinaCommon overseasBasic#structured-output#schema-validation

  How to reason about it · think before answering

  1. The real question is the second half. Answering only use JSON mode signals you have never run this in production, because all the work happens after validation fails.
  2. Lay out three paths: prompt constraints plus local validation; a vendor's JSON mode or structured-output parameter; or defining the data structure as a tool's parameter schema. Vendor support and field names differ, so the latter two bind that code to one vendor.
  3. State the selection rule: cross-vendor or offline-capable means path one, paying with your own JSON extraction and validator; single-vendor and success-rate-driven means use their structured output. Extraction must handle code fences and surrounding chatter — parsing the whole reply directly breaks often.
  4. Handle failure as a ladder, not just a retry: feed the path-annotated issues back and ask it to fix only those (more effective than upgrading the model); then degrade to a minimal required-fields-only structure; then fail the round and persist the artifact for a human — never swallow the error and return an empty array.
  5. High-signal point: validate in two layers. Type and range checks catch malformed data but not wrong references — a nonexistent scene id or a duplicate shot number passes typing and explodes downstream. Referential integrity needs its own pass.
  6. Likely follow-up: how many retries? Two. The first covers a disobedient model; if it still fails with concrete issues in hand, the prompt or the schema itself is wrong and more retries just buy the same error.

  分析过程 · 先想清楚再作答

  1. 这题的题眼在后半句。前半句答「用 JSON 模式」就结束的人，等于说自己没在生产里跑过——真正的活儿全在校验失败之后。
  2. 先把三条路摆开：提示词约束加本地校验；厂商提供的 JSON 模式或结构化输出参数；把数据结构定义成工具的参数 schema 让模型去调。各家对后两条的支持程度和字段名都不一样，选它就等于把这段代码绑在某一家上。
  3. 给出选择依据：要跨厂商、要能离线跑，就选第一条，代价是自己写抠 JSON 与校验；只服务一家且追求成功率，就用那一家的结构化输出。抠 JSON 这一步必须处理围栏与前后寒暄，直接解析整段回复在真实模型上很容易炸。
  4. 校验失败的处理是一条阶梯，别只答重试：把带路径的问题原样喂回去让它只修这些（比换更大的模型有效）；仍不过就降级到只要必填字段的最小结构；再不过就整轮失败并留档，让人来看，而不是吞掉异常返回一个空数组。
  5. 还有一条区分度很高：校验要分两层。判类型与范围只能挡住格式错，挡不住写错对象——引用了不存在的场景 id、镜号重复，这类稿子能通过类型检查，然后在下游某一步才爆。引用完整性必须单独查一遍。
  6. 可预期的追问：重试几次合适？两次。第一次是模型没听话，第二次带着具体问题还改不对，说明是提示词或 schema 本身有问题，再重试只是花钱买同一个错误。

  Key points

  • Three paths: prompt plus local validation, vendor structured output, or tool parameter schema — the latter two bind you to a vendor
  • JSON extraction must handle code fences and surrounding prose; never parse the whole reply directly
  • Failure handling is a ladder: feed back path-annotated issues, degrade to a minimal structure, then fail the round and persist for a human
  • Validate in two layers — types and ranges, then referential integrity and id uniqueness
  • Cap retries at two; beyond that the prompt or schema is wrong, not luck

  答题要点

  • 三条路：提示词加本地校验、厂商结构化输出参数、工具参数 schema，后两条会绑定厂商
  • 抠 JSON 要处理围栏与前后寒暄，不能直接解析整段回复
  • 失败处理是阶梯：带路径的问题喂回去只修这些、降级到最小结构、整轮失败留档给人
  • 校验分两层，类型与范围之外必须单独查引用完整性与 id 唯一性
  • 重试上限两次，再不过说明是提示词或 schema 的问题，不是运气问题

D3 Character Consistency: Character Sheets, Reference Images, and Style Locking — Keeping the Same Person the Same Person in Every Shot

• Where does the character consistency problem in image generation come from, and what engineering mitigations exist, with what trade-offs?生成模型的角色一致性问题是怎么来的？工程上有哪几种缓解手段，代价分别是什么？

  Common in ChinaCommon overseasBasic#image-generation#consistency

  How to reason about it · think before answering

  1. The differentiator is your first sentence. Saying 'the prompt wasn't detailed enough' reads as a user, not an engineer; the answer they want is that each request is an independent sample with no memory across calls.
  2. Follow the mechanism: a prompt only constrains the degrees of freedom you actually wrote down, and everything unwritten gets re-sampled — while face recognizability lives exactly in the details text cannot exhaust.
  3. Present the mitigations in three layers by what each one actually locks: a prompt template locks style and framing at near-zero cost; a fixed seed locks reproducibility for one identical prompt and stops helping the moment the prompt changes; a reference image locks the face, but only one per request, so two faces in one frame cannot both be locked.
  4. The trade-off discussion is where candidates separate: using a reference image means you must first produce a base image, which forces a human 'pick the reference sheet' step into an otherwise unattended pipeline.
  5. Volunteer the counter-intuitive rule: every derived image must reference the same base image, never the previous one. Chaining references accumulates drift, and by the fifth image it is a different person.
  6. Expect the follow-up: what if consistency still fails? The answer is cinematography — split two-character frames into reverse-angle singles and push secondary characters to wider shots, working around the API's limits with shot design.

  分析过程 · 先想清楚再作答

  1. 这题的区分度在第一句。答「提示词写得不够细」就掉到了使用者视角；面试官想听的是「模型每次请求都是独立采样、没有跨请求记忆」这个机制层面的原因。
  2. 顺着机制往下推就有了完整答案：提示词只约束了你写出来的那些自由度，没写的部分每次重新掷一遍；而人脸的辨识度恰好集中在脸型、眼距、鼻梁这些你没法用文字穷尽的细节上。
  3. 手段按「锁得住什么」分三层说，不要混在一起：提示词模板锁风格与构图，成本几乎为零；随机种子锁同一提示词的可复现性，换提示词即失效；参考图锁人脸，但每次请求只能带一张，双人同框锁不了两个人。
  4. 代价这一段才是拉开差距的地方：参考图要求你先有一张基准图，于是流程里必须插入一次「定妆并由人挑一张」的环节，这是整条自动化流水线上少数值得保留的人工卡点。
  5. 还要主动说一个反直觉的做法：派生图必须都参考同一张基准图，不能参考上一张。参考上一张会让偏差逐张累积，第五张已经不是同一个人了。
  6. 可以预期的追问：一致性做不到怎么兜底？答案是改镜头语言——把双人同框拆成正反打的单人镜头、次要角色用更远的景别，用拍法回避接口能力的边界。

  Key points

  • The root cause is that each request is an independent sample with no cross-request memory, so unconstrained degrees of freedom get re-rolled
  • A prompt template locks style and framing at near-zero cost but cannot lock facial detail
  • A fixed seed locks reproducibility for one identical prompt and stops helping once the prompt changes
  • A reference image locks the face, but you must first produce a base image and only one reference is allowed per request
  • Derive every variant from the same base image rather than chaining off the previous one, or drift accumulates image by image

  答题要点

  • 根因是模型每次请求独立采样、没有跨请求记忆，提示词没约束到的自由度会被重新掷一遍
  • 提示词模板锁风格与构图，成本几乎为零，但锁不住五官
  • 随机种子锁的是同一提示词的可复现性，提示词一变就失效
  • 参考图锁人脸，代价是必须先有基准图，且每次请求只能带一张，双人同框锁不了两个人
  • 派生图统一参考同一张基准图，不要链式参考上一张，否则偏差会逐张累积

D4 From Shot to Footage: Image-to-Video, Polling Async Tasks, and Retrying Failures

• How do you choose a polling interval, and why is a fixed interval a bad default?轮询间隔怎么定？为什么不能一直用固定间隔死等？

  Common in ChinaCommon overseasBasic#async-task#backoff

  How to reason about it · think before answering

  1. This looks like a giveaway, but it has three layers and only the first one is obvious. They want to know whether you have actually written this loop.
  2. Layer one is cost: a task queued for five minutes polled every second is three hundred wasted requests. The query endpoint has its own rate limit, so you can throttle yourself and then misread 'rate limited' in the logs as a generation problem.
  3. Layer two is capping the backoff: multiply without a cap and you end up polling every few minutes, sleeping long after the task finished. Pick the cap from what extra wait a user tolerates — usually in the ten-to-twenty-second range.
  4. Layer three is where people actually get it wrong: the timeout check belongs before the sleep, and the test is whether sleeping would cross the deadline. Sleeping first means overshooting the budget by a full interval, which at a twenty-second backoff is twenty wasted seconds.
  5. Mention ordering too: check terminal states before the timeout. Discarding a task that just succeeded on the final poll means paying for an artifact you then throw away.
  6. Expect the follow-up: how do you pick the initial interval? From the typical duration of this class of task, a bit above a tenth of it; and the very first poll can be delayed slightly, since a just-submitted task is almost never done.

  分析过程 · 先想清楚再作答

  1. 这是一道送分题，但它有三个层次，只答出第一层拿不到高分。面试官想看的是你有没有真的写过这个循环。
  2. 第一层是成本：一个排队五分钟的任务，用一秒的固定间隔就是三百次无效请求。查询接口自己也有速率限制，你很可能自己把自己打到限流，然后在日志里看到「生成失败：限流」，还以为是生成接口的问题。
  3. 第二层是退避要封顶：只乘不封顶的话，退到后面已经是几分钟查一次，任务早就好了你还在睡。上限的选法是「用户能忍受的额外等待」，一般十几到二十秒。
  4. 第三层最容易写错，也是这题真正的区分点：超时判断必须放在睡觉之前，判据是「睡下去会不会越过截止时间」。先睡再判会让你在预算之外多睡整整一轮，退避到二十秒时就是白等二十秒。
  5. 另外提一条顺序：先判终态再判超时。任务恰好在最后一次查询里成功却被当成超时扔掉，等于付了钱还丢了产物。
  6. 可以预期的追问：起步间隔怎么定？按这类任务的典型耗时定，比典型耗时的十分之一略大即可；再往细说就是首次查询可以稍微延后一点，因为刚提交的任务几乎不可能立刻完成。

  Key points

  • A fixed interval is either too tight, wasting requests and throttling yourself, or too loose, adding dead time after completion
  • Use exponential backoff starting near a tenth of the task's typical duration
  • Cap the backoff, choosing the cap from the extra wait a user will tolerate
  • Check the timeout before sleeping, testing whether the sleep would cross the deadline, or you overshoot the budget by a full interval
  • Check terminal states before the timeout so a task that just succeeded is not discarded

  答题要点

  • 固定间隔要么太密造成大量无效请求并把自己打到限流，要么太疏让完成后的等待过长
  • 用指数退避：从接近典型耗时十分之一的间隔起步，每轮乘一个系数
  • 退避必须封顶，上限按用户能忍受的额外等待来定
  • 超时判断放在 sleep 之前，判据是「睡完会不会越过截止时间」，否则会在预算之外多睡一轮
  • 先判终态再判超时，避免把最后一次查询里刚成功的任务误杀

D5 Voiceover, Subtitles, and Audio Tracks: Multi-Character Voices, Timeline Alignment, and Subtitle Files

• In a multi-character pipeline, how do you guarantee the same character keeps the same voice across episodes?多角色配音里，怎么保证同一个角色跨集用的是同一个声音？

  Common in ChinaCommon overseasBasic#tts#consistency#provider-abstraction

  How to reason about it · think before answering

  1. This looks like a voice question but is really about where state lives. 'Hardcode it in config' is not wrong, but stopping there shows no engineering judgment.
  2. Name the risk first: voice is part of a character's identity, and audiences are about as sensitive to it as to a face. Inconsistency across episodes has three usual causes — running each episode as an independent pipeline, picking voices from an ad-hoc or random mapping, and someone tweaking a character's global parameters while fixing the delivery of one line.
  3. The fix is to file the voice in the character record rather than in code: the record carries a voice id, and the dubbing step only reads it. Consistency then holds regardless of episode, run or operator — the same pattern as pinning appearance to a base reference image.
  4. Storing the voice id alone is not enough. Perceived sameness also depends on the baseline emotion and the speaking rate; the same voice at two different rates sounds like a different state of a person. Keep all three in the record, and allow per-line overrides of emotion only, never of rate.
  5. Add a defensive layer: record the voice id together with the model name in the artifact metadata. Vendors do retire and rename voices, and you want to be able to answer 'why does season two sound different' from data rather than memory.
  6. Expect the follow-up: what if the vendor retires that voice? Make voice selection part of the provider abstraction — the record stores the character's voice archetype, and the mapping to a concrete vendor voice lives in the adapter, so swapping vendors never touches the character records.

  分析过程 · 先想清楚再作答

  1. 这题看着像配音问题，其实考的是状态该存在哪里。答「配置里写死」不算错，但只答到这一层看不出工程判断。
  2. 先说清楚风险来自哪：声音是角色身份的一部分，观众对它的敏感度不低于脸。跨集不一致的典型成因有三个——每集独立跑一次流程、音色靠临时映射或随机挑选、以及某次为了改一句台词的语气顺手改了这个角色的全局参数。
  3. 解法是把音色归档而不是归代码：角色档案里带一个音色字段，配音环节只读不写。这样一致性由档案保证，跟哪一集、哪一次运行、谁跑的都无关。这跟角色形象靠基准图归档是同一套思路。
  4. 但只存音色标识还不够，跨集听感一致还依赖另外两项：基调情绪与语速。同一个音色用两种语速念，听起来像两个人的状态。所以档案里要一起存这三项，单条台词只允许覆盖情绪，不允许覆盖语速。
  5. 再补一层防御：把音色标识连同模型名一起记进产物元数据。厂商下线或重命名一个音色是会发生的，你要能查出「第二季为什么听起来不一样」，而不是只能凭记忆猜。
  6. 可以预期的追问：如果厂商真的下线了那个音色怎么办？答案是把音色选择也做成 provider 抽象的一部分：档案里存的是角色的音色角色定位，映射到具体厂商音色的表放在适配层，换厂商或补映射时不动档案。

  Key points

  • Store the voice in the character record and have the dubbing step read it only, so consistency is independent of episode, run or operator
  • Keep voice id, baseline emotion and speaking rate together; allow per-line emotion overrides but never rate overrides
  • Write the voice id and model name into artifact metadata so you can explain why a later season sounds different
  • Typical causes of drift are per-episode independent runs, ad-hoc mappings, and global tweaks made while fixing one line
  • Fold voice selection into the provider abstraction: records hold the archetype, the adapter maps it to a concrete vendor voice

  答题要点

  • 把音色存进角色档案，配音环节只读不写，一致性与集数、运行次数、操作人无关
  • 档案里要同时存音色标识、基调情绪与语速；单条台词只允许覆盖情绪，不允许覆盖语速
  • 把音色标识与模型名一起写进产物元数据，便于回答「为什么这一季听起来不一样」
  • 跨集不一致的典型成因是每集独立跑、临时映射、以及改一句台词时顺手改了全局参数
  • 音色选择应纳入 provider 抽象：档案存角色的音色定位，具体厂商音色的映射放在适配层

D6 The Editing Bay: Assembling Footage Into One Vertical Cut With ffmpeg

• When can you concatenate video segments without re-encoding, and when must you re-encode?把多个视频片段拼成一条完整的视频，什么时候可以不重新编码，什么时候必须重编码？

  Common in ChinaCommon overseasBasic#ffmpeg#encoding#media-pipeline

  How to reason about it · think before answering

  1. This is a giveaway concept question, but it only gives points to people who state the precondition. 'Just use concat' and 'stream copy requires identical parameters' read as two different levels.
  2. There is exactly one criterion: does concatenation only need to move packets into a new container in order? If yes, stream copy works. If even one frame has to be newly computed, you must re-encode.
  3. Be able to recite the preconditions: resolution, frame rate, pixel format, codec, audio sample rate and channel layout must all match. Miss one and you get corruption, dropped audio, or a broken duration.
  4. Cases that force re-encoding: transitions (those frames are new), scaling and padding to a common canvas, mixing in a new audio track, or changing encoding parameters. AI-generated material varies in size and often lacks audio, so normalization is almost always required in practice.
  5. The conclusion is a combination: normalize each shot with its own filter graph pass, then stream-copy the now-identical segments together. Total re-encoding is still one pass, but you gain full control over each shot.
  6. Expect the follow-up 'how do you know whether the parameters match'. Answer: read the key fields of each segment with ffprobe and compare. That precheck belongs in any automated pipeline.

  分析过程 · 先想清楚再作答

  1. 这是一道概念送分题，但送分的是「说出前提」的人。答「用 concat 就行」和答「参数一致才能流拷贝」，在面试官眼里是两个水平。
  2. 判据只有一条：拼接是不是只需要把数据包按顺序搬进新容器。只搬不算，就能流拷贝；只要有任何一帧画面是新算出来的，就必须重编码。
  3. 流拷贝的前提要能背出来：分辨率、帧率、像素格式、编码器、音频采样率、声道数全部一致。差一项，产物要么花屏掉音，要么时长错乱。
  4. 必须重编码的典型场景：转场（那几帧是新画面）、缩放补边到统一画布、混入新的音轨、改变编码参数。AI 生成的素材尺寸和音轨天然不一致，所以实际工程里几乎总要先归一化。
  5. 结论落在一个组合拳上：每一镜单独走一次滤镜图做归一化，然后用流拷贝把参数已经一致的片段拼起来。重编码的总量还是一遍，但换来了对每一镜的完全控制。
  6. 可预期的追问是「怎么判断素材参数一不一致」。答：用 ffprobe 把每段的关键字段读出来做一次比对，不一致就走归一化，这一步也是自动化流水线里必须有的前置检查。

  Key points

  • The criterion is whether concatenation only moves packets: if so, stream copy; if any frame is newly computed, re-encode.
  • Stream-copy preconditions: identical resolution, frame rate, pixel format, codec, sample rate and channel layout.
  • Transitions, scale-and-pad, mixing a new audio track, and changing encoding parameters all force re-encoding.
  • The practical combination: normalize per shot first, then stream-copy concatenate. Total re-encoding stays at one pass.
  • Use ffprobe to compare segment parameters as a pipeline precheck.

  答题要点

  • 判据是拼接是否只需要搬数据包：只搬就能流拷贝，有新算出来的帧就必须重编码。
  • 流拷贝的前提：分辨率、帧率、像素格式、编码器、采样率、声道数全部一致。
  • 转场、缩放补边、混入新音轨、改编码参数，这几类一定要重编码。
  • 实践中的组合拳：先逐镜归一化，再流拷贝拼接，重编码总量仍是一遍。
  • 用 ffprobe 比对各段参数，作为流水线里的前置检查。

D7 One Episode Wrapped: Stringing Six Stages Into an End-to-End Pipeline and Tallying the First Bill

• How do you measure the cost of a generation pipeline, and what besides money should you measure?怎么度量一条生成流水线的成本？除了钱还要量什么？

  Common in ChinaCommon overseasBasic#observability#cost-accounting#pipeline-design

  How to reason about it · think before answering

  1. This looks like a giveaway, but the real question is 'besides money'. Anyone who reports a single total cannot make an optimization decision, because a total does not say where to act.
  2. First decide the granularity: break it down per stage. One number carries no information; a per-stage table immediately shows where the money and the time went. Measured on one episode here: five images cost 0.125 yuan, voice under two cents, three video shots 10.5 yuan — video is 98 percent. You only see that broken down.
  3. Second, measure three things besides money: elapsed time decides how many episodes per day, call count decides whether you hit provider rate limits, and artifact count is the crudest completeness check — four shots should yield four clips, and a missing one means something failed silently.
  4. Third, separate estimates from real spend. Offline or in load tests you have no real amounts, so derive them from published unit prices — but label them as estimates, and never mix the two on one code path or the books will never reconcile.
  5. Also worth flagging: offline timing rankings are usually fake. With the APIs stubbed, local encoding becomes the biggest slice, and optimizing against that chart targets the wrong thing.
  6. Expect the follow-up 'what do you optimize first'. Answer: whatever has a number attached. Here it is waste from failed reruns, because it equals money on the bill. Concurrency comes second — before output is stable, concurrency only burns money faster.

  分析过程 · 先想清楚再作答

  1. 这题看着是送分题，题眼其实在「除了钱」。只报一个总金额的人，做不出任何优化决策，因为总金额不告诉你该动哪里。
  2. 第一步是确定度量的粒度：**按环节摊开**。一个总数没有信息量，一张按环节分列的表能立刻告诉你钱花在哪、时间花在哪。本课量过一集：五张图一毛二五、配音不到两分、三个镜头的视频十块五，视频占了九成八——这个结论只有摊开才看得见。
  3. 第二步是把「钱」之外的三样一起量：耗时决定一天能出几集；调用次数决定会不会撞上厂商的速率限制；产物数是最朴素的完整性校验，四个镜头就该有四个视频，少一个说明某处静默失败了。
  4. 第三步是把估算和真实分开。离线或压测时拿不到真实金额，可以按公开单价折算，但**必须标明它是折算值**，而且折算逻辑和真实金额不能混在一条路径上算，否则账永远对不上。
  5. 还要提醒一句常被忽略的：离线模式下的耗时排名往往是假的。接口被打了桩，本地的编码步骤反而成了大头，照着这张图做优化会优化错地方。
  6. 可预期的追问是「量完之后先优化哪一项」。答：先优化能被数字证明收益的那一项。这个场景里是失败重跑造成的浪费，因为它直接等于账单上的金额；并发排第二，因为在产出还不稳定时并发只会让你更快地烧钱。

  Key points

  • Break the cost down per stage; a single total cannot tell you where to act.
  • Besides money, measure elapsed time, call count and artifact count — throughput, rate limits and completeness.
  • Keep estimated and real spend on separate paths, and always label estimates as estimates.
  • Offline timing rankings are unreliable; do not optimize against a stubbed profile.
  • Prioritize by which improvement has a number attached, not by intuition.

  答题要点

  • 按环节摊开，不要只给一个总数，否则无法定位该优化哪里。
  • 除了金额还要量耗时、调用次数、产物数，各自对应吞吐、限流、完整性。
  • 估算与真实金额分开计算，估算必须标明是折算值。
  • 注意离线模式下耗时排名不可信，别照着假图做优化。
  • 优化顺序按「收益能不能被数字证明」排，不按直觉排。