next-exp / next-exp/IC

Parallel threads

Open
#528 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

docs
Dominant language
Python
Stars
11
Forks
77
PR merge metrics
No merged PRs in 30d

Description

I'm not sure if it's an IC problem, just tell me if it is not.
I've been running diomira in the majorana1 queue system and I noticed that it was extremely slow, much more (> 10 times) than if I ran in the same machine interactively.
I've asked José Vicente about it and he says that each process is being parallelized to 44 threads and this is the reason why everything is so slow. I don't have any number of threads defined in my scripts for the queue system (and I haven't changed them lately), so I was wondering if there have been any changes in the IC code that could affect the thread parallelization. I'm totally ignorant about this topic, so if anyone can help me, I'd be grateful.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the slowdown in the majorana1 queue system versus an interactive run, using the reported diomira workload. Inspect the IC code and the queue-run scripts for how process thread counts are selected. Done means determining whether IC causes the 44-thread parallelization and documenting or addressing the cause.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.