aws / aws/sagemaker-rl-container

Using redis on system memory instead of GPU memory.

Open
#25 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
82
Forks
44
PR merge metrics
No merged PRs in 30d

Description

Hi.

Good day.

Is it possible to not run redis on the GPU? At the moment I am getting the following error using it training deep racer:
```
subscribe scheduled to be closed ASAP for overcoming of output buffer limits
```

It seems as though the process wants to allocate gigs of memory into redis but the GPU only has about 7GB, whereas the system has free memory to use.

I'm just not sure how to get it to use the CPU. I tried creating an image myself and making the following change to start.sh:
```
CUDA_VISIBLE_DEVICES=-1 redis-server --bind 0.0.0.0 &
```

But when I run the image it doesn't use GPU at all.

Any ideas how to have redis use the systems memory and not the GPU memory? Thanks.

Regards.

Contributor guide

Open the contributing guide

Research direction

Start with the start.sh entry point and the redis-server invocation shown in the issue, then reproduce the container's memory behavior during DeepRacer training. Check whether the Redis process and the rest of the image retain the expected GPU access; done means Redis uses system memory without preventing the container from using the GPU.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, redis
Domain
databases, devops
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.