Skip to content

Compute requirements for code-server #232

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jgbradley1 opened this issue Mar 13, 2019 · 14 comments
Closed

Compute requirements for code-server #232

jgbradley1 opened this issue Mar 13, 2019 · 14 comments

Comments

@jgbradley1
Copy link

Can general guidance be provided somewhere in the README on the recommended minimum compute requirements are for code-server to function correctly?

This will help people who are interested in self-hosting. There are some memory/cpu issues right now that have to be accounted for. I'm also wondering how it compares to the desktop VS Code requirements.

@sr229
Copy link
Contributor

sr229 commented Mar 13, 2019

You need at least 2GB of RAM to run Coder and a CPU that is 64 bit, and is x86_64. The reason why 2GB is required because the server eats at least 1-1.4GB in average

@wcypierre
Copy link

@sr229 I've allocated 4gb of ram and ran it on a folder with no files under it and it still doesn't work though

@sr229
Copy link
Contributor

sr229 commented Mar 16, 2019

It does not relate to your specs, I need your system info and diagnostic logs @wcypierre

@wcypierre
Copy link

@sr229 where can I extract the logs from?

@sr229
Copy link
Contributor

sr229 commented Mar 16, 2019

if you launch the binary manually, the log output is in stdout. If by SystemD, use journalctl

@SuperSandro2000
Copy link
Contributor


Around this on idle. Can't explain the jitter.

@ruslanguns
Copy link

ruslanguns commented Apr 21, 2019

I created a dropplet 5$ for testing coder and got an issue that breaks since the buffer:

root@ruso:~# code
(node:1255) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
INFO  code-server v1.903-vsc1.33.1
INFO  Additional documentation: http://github.com/codercom/code-server
INFO  Initializing {"data-dir":"/root/.local/share/code-server","extensions-dir":"/root/.local/share/code-server/extensions","working-dir":"/root","log-dir":"/root/.cache/code-server/logs/20190421115346166"}
INFO  Starting webserver... {"host":"0.0.0.0","port":8443}
INFO
INFO  Password: 44a8e1776f389e43792aec9b
INFO
INFO  Started (click the link below to open):
INFO  http://localhost:8443/
INFO
INFO  Starting shared process [1/5]...
WARN  stderr {"data":"(node:1279) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.\n"}
INFO  Connected to shared process
INFO  WebSocket opened / {"client":1,"ip":"47.63.161.195"}
internal/child_process.js:366
    throw errnoException(err, 'spawn');
    ^

Error: spawn ENOMEM
    at ChildProcess.spawn (internal/child_process.js:366:11)
    at Object.spawn [as _spawn] (child_process.js:538:9)
    at t.async (/home/travis/build/codercom/code-server/packages/server/out/cli.js:504:34598)
    at e.exports (/home/travis/build/codercom/code-server/packages/server/out/cli.js:504:34099)
    at e (/home/travis/build/codercom/code-server/packages/server/out/cli.js:504:32722)
    at Timeout.u [as _onTimeout] (/home/travis/build/codercom/code-server/packages/server/out/cli.js:504:33015)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)

image

Something is wrong...

Edited:: .....
By the way... it is happening the last release, the prior one is working... so I think this is a bug.

@sr229
Copy link
Contributor

sr229 commented Apr 21, 2019

It's not a bug according to the stack trace, code-server once has a running interactive session in the browser will begin to spike on RAM usage to 1GB (RIP Raspberry Pi users)

@ruslanguns
Copy link

Also RIP to low budget users for DO Droplets lol.

Thanks for response it is good to know.

@bensonokiora
Copy link

bensonokiora commented Apr 22, 2019

Am getting the same error with a new 2GB Ram Droplet
Capture
Duplicate of #

@sr229
Copy link
Contributor

sr229 commented Apr 25, 2019

@bensonokiora I don't think this relates to this issue at all.

@sr229
Copy link
Contributor

sr229 commented Apr 25, 2019

@ruslanguns there is a way to run it on a 1GB environment

Swapping is a marvelous ad dangerous way to extend the lifespan of your server

@ruslanguns
Copy link

I ll check that... thanks! 👍

@code-asher
Copy link
Member

code-asher commented Oct 23, 2019

v2 requirements should be lower than v1 and are documented here: https://github.com/cdr/code-server#requirements

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants