AsyncResult and px: groupby='first', groupby='merge'
- Linguagem predominante
- Jupyter Notebook
- Estrelas
- 2.6k
- Forks
- 1k
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Descrição
The current groupby argument always displays the result of all engines.
It is useful sometimes to only display the result of a single engine -- when the execution / result is known to be symmetric. I propose adding a groupby argument:
- `first` : only display the result of the engine id 0; results from other engines are consumed and abandoned.
- `merge` : only display the unique results. For example, if engine 0 to 3 have identical results, and engine 4-8 have another identical results, then a two sets of results are displayed. The interactive debugger from intel mpi (a wrapper of gdb with result-merging) has this feature.
The merge mode is much harder in this case, because 'identical' is difficult to define -- objects have been serialized and deserialized; id is different. Using hash may be a possibility.
The `first` mode will already be very handy in trimming down the verbosity in a lot of cases.
Guia de contribuição
Direção de pesquisa
Start by reading the existing AsyncResult groupby handling and the px entry point referenced in the issue. Define the behavior for groupby='first', including consuming other engine results, then inspect how existing tests cover grouped output; done means the first-engine result is shown without the other engines' output.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- jupyter, python
- Domínio
- distributed-systems
- Tipo de issue
- Funcionalidade
- Dificuldade
- 5/5
- Tempo estimado
- Mais de uma semana
- Status de atividade
- Estagnada
- Clareza
- Razoavelmente clara
- Facilidade para iniciantes
- 25/100