Parallel Letter Frequency times out in the web interface
- Lenguaje dominante
- Ruby
- Estrellas
- 601
- Forks
- 532
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
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.
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Evaluación
Este issue todavía no se ha evaluado.