Skip to content

Commit 36bae47

Browse files
authored
Update FAQ by removing outdated local machines section
Removed section about local machines and shared memory issues.
1 parent 71d3fb4 commit 36bae47

File tree

1 file changed

+0
-6
lines changed

1 file changed

+0
-6
lines changed

docs/faq/README.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -38,9 +38,3 @@ Hyperloop trains have a so-called express train feature. This feature is based o
3838
### Why is it that my train test has a CPU warning but my wagon test was fine?
3939

4040
This usually happens in a situation where the wagon test (which runs on a single core) uses so much memory that it doesn't fit a single core job on the grid and therefore needs two cores for the train (more cores means a higher memory allowance). But if the devices in the wagon cannot be parallelised well over multiple cores, this leads to more wall time and a higher CPU usage as the cores will be underutilised. In this situation, one can either reduce the wagon memory consumption to fit into a single core or reduce the CPU consumption to fit the dataset.
41-
42-
## Your local machines
43-
### `shmem: could not create a message of size ...`
44-
45-
Add `--shm-segment-size 1000000000` (or larger number) to your o2 command.
46-
It is due to shared memory segment that is probably outdated for the size of the intermediate tables you have. It is actually set as 90% of system's max VSIZE allowance set in limits, or 2GB if the limits cannot be found, which is probably what happens in your case.

0 commit comments

Comments
 (0)