Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Parallel Letter Frequency times out in the web interface

未关闭
#1,642 7 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
ruby

调研方向

先从 issue 中提到的 Parallel Letter Frequency 测试和 test_faster_than_serialized_answer 基准测试开始,然后在 Exercism 基础设施上复现超时,而不只是进行本地复现。将串行基准测试的开销与可用的超时时间和并行度进行比较,并确定问题是由基准测试输入还是执行限制导致的。完成的标准是:练习的示例和社区解决方案都能在基础设施限制内完成,并且基准测试的行为已由测试覆盖。

由索引模型根据 Issue 内容生成。

描述

In my local environment, my solution passes all tests in 1.4 seconds. Of this time, about 70% is spent running the serial solution in test_faster_than_serialized_answer. When this is run on the Exercism infrastructure, my solution times out. For giggles, I tried the example solution from this repo and this also times out. If I make my solution do nothing so that all of the time spent in the Exercism infrastructure is due to the serial solution, it doesn't time out, but obviously it doesn't pass the tests.

It seems that Exercism runners aren't fast enough or don't have enough parallelism to allow a parallel solution to run in the small amount of time left over after accounting for the fixed cost of the serial benchmark solution. Is it actually possible to have a solution succeed when running on the Exercism infrastructure? If not, can we reduce the size of the benchmark input to allow a solution to succeed?

Note that after submitting my failing solution, I saw that no community solutions are listed. Presumably this means that no one has a solution that can run in the time allotted.

主要语言
Ruby
星标
598
派生
531
平均合并
13 小时 44 分钟
30 天内合并 PR
8

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

exercism/ruby 的其他 Issue

查看 exercism/ruby 的全部 Issue

相似的 Issue

更多 Ruby Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。