Starting object store with directory /dev/shm and huge page support disabled
See original GitHub issueWhen the docker starts I get
/arrow/cpp/src/plasma/store.cc:1226: Allowing the Plasma store to use up to 0.4GB of memory. /arrow/cpp/src/plasma/store.cc:1253: Starting object store with directory /dev/shm and huge page support disabled
I am not sure if I am doing the shm_size setting correctly, I have it installed on Unraid with Extra Parameters “–shm-size=1024m”.
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (3 by maintainers)
Top Results From Across the Web
Should I be concerned about this message "The object ...
You may be able to free up space by deleting files in /dev/shm. If you are inside a Docker container, you can increase...
Read more >When should I use /dev/shm/ and when should I use /tmp
/dev/shm is a temporary file storage filesystem, i.e., tmpfs, that uses RAM for the backing store. It can function as a shared memory...
Read more >[Python] test_plasma.py fails (in test_plasma_list)
../src/plasma/store.cc:956: Starting object store with directory /dev/shm and huge page support disabled I'm not sure whether there's ...
Read more >Changes in object store eviction behavior with latest ray ...
external/plasma/cpp/src/plasma/store.cc:1030: Starting object store with directory /dev/shm and huge page support disabled.
Read more >SDP Data Access Library - SKAO - GitLab
/arrow/cpp/src/plasma/store.cc:1269: Starting object store with directory /dev/shm and huge page support disabled.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
So I was able to solve the issue by switching to another usb port.
I found out when coral is plugged into a teal blue USB 3.0 10Gbps (USB 3.2 Gen2) port it will only run at USB 2.0 speed (~24ms latency), and when plugged into a normal dark blue USB 3.0 (USB 3.2 Gen1) port it will run at normal 3.0 speed (~8ms latency). I suspect it’s a Linux driver issue, but it doesn’t really matter anyway since I have plenty normal dark blue USB 3.0 (USB 3.2 Gen 1) ports.
Man I hate those new USB naming scheme.
I don’t think it’s a cable issue. I too am using the cable that came with the Coral.