Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

I am using ubuntu 18.04 1GB/25GB droplet.
⠇ building for production...
<--- Last few GCs --->
[13356:0x2d01d20] 47970 ms: Scavenge 419.9 (477.4) -> 419.9 (477.4) MB, 2010.2 / 16.4 ms allocation failure
[13356:0x2d01d20] 53123 ms: Scavenge 420.0 (477.4) -> 419.9 (477.4) MB, 5087.1 / 13.7 ms allocation failure
[13356:0x2d01d20] 55738 ms: Scavenge 420.0 (477.4) -> 420.0 (477.4) MB, 2579.4 / 6.1 ms allocation failure
[13356:0x2d01d20] 63980 ms: Scavenge 420.0 (477.4) -> 419.9 (480.4) MB, 8227.6 / 137.3 ms allocation failure
<--- JS stacktrace --->
Cannot get stack trace in GC.
FATAL ERROR: NewSpace::Rebalance Allocation failed - process out of memory
1: node::Abort() [node]
2: 0x8c20ec [node]
3: v8::Utils::ReportOOMFailure(char const*, bool) [node]
4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [node]
5: 0xa2f43b [node]
6: v8::internal::MarkCompactCollector::Evacuate() [node]
7: v8::internal::MarkCompactCollector::CollectGarbage() [node]
8: v8::internal::Heap::MarkCompact() [node]
9: v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [node]
10: v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
11: v8::internal::Factory::NewUninitializedFixedArray(int) [node]
12: 0xd4af53 [node]
13: v8::internal::Runtime_GrowArrayElements(int, v8::internal::Object**, v8::internal::Isolate*) [node]
14: 0x377335b042fd
Aborted
npm ERR! code ELIFECYCLE
npm ERR! errno 134
npm ERR! hashfav@1.0.0 build: `node build/build.js`
npm ERR! Exit status 134
npm ERR!
npm ERR! Failed at the hashfav@1.0.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-06-27T06_15_55_973Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 134
npm ERR! hashfav@1.0.0 start: `npm run build && node server.js`
npm ERR! Exit status 134
npm ERR!
npm ERR! Failed at the hashfav@1.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-06-27T06_15_56_005Z-debug.log
WildcatMedia
jeffs
0621335d663b4b699a60eb27e28153
accesstrax
Dwight Trumbower
admin
yimprogramming
samunyi90
1d6ce141ab5444dfb1ea2dd29cf4b1
Matt Fricker
joel9b158e40551b15093f213f