You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I set line 50 of package.json to: "mongodb": "^3.7.3",
But also line 29 to: "@types/mongodb": "^3.6.20",
From the package site, it's the only current v3 tag for mongodb. Such an update, from v3.5.6, is essential if I install the latest version of mongodb in VirtualBox (debian), although there are quite a few config settings which would probably work with v3.5.6, but a simple update fixes the problem I had by default.
(Update: I forgot about @types/mongodb needing update too, because it takes about 24 hrs for a timeout to occur. I figured that out by accident & then completely forgot after I destroyed the installation by updating other things. Only mongodb & @types/mongodb need updating, except it takes a couple days more testing to be sure. v4 of mongodb won't work.)
Also in this json I replaced 8192 (MB) on line 9 with 65536, since I prefer 64GiB of virtual NVMe™ SSD memory. In /etc/mongod.conf I lifted the memory limit: cacheSizeGB: 128. In config.ts I disabled telemetry on line 93, & lifted the timeout on line 27 (just in case, but prob does nothing since I use only BCHD grpc).
NB: Any other dependency update seems a bad idea unless done very carefully. e.g. updating slpjs@^0.27.8 to slpjs@^0.27.9 breaks the entire node_modules directory, forcing me to reconstruct all modules all over again. slpjs@^0.27.8 is deprecated btw, & could help explain why my syncing is so slow. I've posted a journal on Reddit, 14 days to block 710k, but only like 13 days without errors (like a timeout after going to sleep, etc). That's all using a Gen2 Intel CPU, though, & I even forgot to "Enable Nested VT-x". I'm not sure SLPJS is using bchdtrustedvalidator properly. An ideal update might be to improve multi-processing, even if that's less efficient than a multi-processing binary (like a little machine written in C++).
I set line 50 of package.json to:
"mongodb": "^3.7.3",
But also line 29 to:
"@types/mongodb": "^3.6.20",
From the package site, it's the only current v3 tag for mongodb. Such an update, from v3.5.6, is essential if I install the latest version of mongodb in VirtualBox (debian), although there are quite a few config settings which would probably work with v3.5.6, but a simple update fixes the problem I had by default.
(Update: I forgot about @types/mongodb needing update too, because it takes about 24 hrs for a timeout to occur. I figured that out by accident & then completely forgot after I destroyed the installation by updating other things. Only
mongodb
&@types/mongodb
need updating, except it takes a couple days more testing to be sure. v4 of mongodb won't work.)Also in this json I replaced 8192 (MB) on line 9 with 65536, since I prefer 64GiB of virtual NVMe™ SSD memory. In
/etc/mongod.conf
I lifted the memory limit:cacheSizeGB: 128
. In config.ts I disabled telemetry on line 93, & lifted the timeout on line 27 (just in case, but prob does nothing since I use only BCHD grpc).NB: Any other dependency update seems a bad idea unless done very carefully. e.g. updating slpjs@^0.27.8 to slpjs@^0.27.9 breaks the entire node_modules directory, forcing me to reconstruct all modules all over again. slpjs@^0.27.8 is deprecated btw, & could help explain why my syncing is so slow. I've posted a journal on Reddit, 14 days to block 710k, but only like 13 days without errors (like a timeout after going to sleep, etc). That's all using a Gen2 Intel CPU, though, & I even forgot to "Enable Nested VT-x". I'm not sure SLPJS is using bchdtrustedvalidator properly. An ideal update might be to improve multi-processing, even if that's less efficient than a multi-processing binary (like a little machine written in C++).
Update: Forgot to mention I've only ever used mongod v6.0.0.
The text was updated successfully, but these errors were encountered: