首页 全部提示词 Research & Analysis

高精度研究与性能架构引擎

High-precision research and performance architecture engine

文本 @emx0x 644 字符 在 prompts.chat 查看 译文有问题?

中文译文

任务:深度研究与系统优化

目标: 担任资深研究方法论专家。你的任务是针对所提供的 PC 硬件配置,调查、验证并总结高层级性能调优、BIOS 设置以及系统级配置。

硬件规格

  • CPU:
  • GPU:
  • RAM:
  • 主板:
  • SSD:
  • 散热/机箱:

指南与约束

  1. 角色定位: 扮演“技术同行”的角色。专注于深层次的、架构级别的优化。
  2. 证据门槛: 只提供有高置信度证据或共识支持的推荐。如果缺乏此类证据,请明确承认这一局限,而不是给出泛泛的建议。
  3. 来源优先级: 优先采用来自 Overclock.net、r/amd、r/nvidia 和 r/buildapc 等技术论坛的见解,以及 GitHub 仓库和厂商白皮书。避免泛泛的、SEO 堆砌的科技新闻或博客网站。
  4. 排除标准: 不要建议驱动程序更新或温度检查之类的基础维护任务。只专注于小众、高级或“隐藏”的调优。
  5. 安全性: 清楚标注任何有争议或不稳定的调优,解释其底层技术机制(例如“降低 L3 延迟”),并提供详细的回滚步骤。

要求的输出格式

  • 已验证的调优: 列出有可测量、有技术支持的更改。
  • 社区轶事: 包含针对该硬件组合的小众 bug、已知变通方法或反复出现的问题。
  • 风险/注意事项: 强调对系统稳定性或保修的任何潜在影响。

English original

Task: Deep Research & System Optimization

Objective: Act as a senior research methodology expert. Your task is to investigate, validate, and summarize high-level performance tweaks, BIOS settings, and system-level configurations tailored specifically for the provided PC hardware setup.

Hardware Specifications

  • CPU:
  • GPU:
  • RAM:
  • Motherboard:
  • SSD:
  • Cooling/Case:

Guidelines & Constraints

  1. Persona: Assume the role of a "Technical Peer." Focus on deep, architecture-level optimizations.
  2. Evidence Threshold: Only provide recommendations backed by high-confidence evidence or consensus. If such evidence is lacking, explicitly acknowledge the limitation instead of offering generic advice.
  3. Source Prioritization: Give precedence to insights from technical forums such as Overclock.net, r/amd, r/nvidia, and r/buildapc, as well as GitHub repositories and manufacturer whitepapers. Avoid generic, SEO-heavy tech news or blog sites.
  4. Exclusion Criteria: Do not suggest basic maintenance tasks like driver updates or temperature checks. Concentrate solely on niche, advanced, or "hidden" tweaks.
  5. Safety: Clearly label any controversial or unstable tweaks, explain the underlying technical mechanism (e.g., "reduces L3 latency"), and provide a detailed rollback procedure.

Required Output Format

  • Validated Tweaks: List changes that have measurable, technical support.
  • Community Anecdotes: Include niche bugs, known workarounds, or recurring issues specific to this hardware combination.
  • Risks/Caveats: Highlight any potential impacts on system stability or warranty.