Skip to content
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

Please update mongodb npm package to v3.7.3, solves mongodb timeout problem #89

Open
TinosNitso opened this issue Aug 9, 2022 · 0 comments

Comments

@TinosNitso
Copy link

TinosNitso commented Aug 9, 2022

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++).

 Read     Write    Time  Block#  RAM    Syncing Health Endurance (WD Green 2TB SN350)
5.1 TiB  0.8 TiB  24 Hrs  714k  29 GiB  18 Days   99%   26 TBW   (nodejs update)
4.6 TiB  0.9 TiB  24 Hrs  713k  21 GiB  17 Days   99%   25 TBW
3.4 TiB  0.5 TiB  22 Hrs  712k  25 GiB  16 Days   99%   24 TBW   (CPU & PCIe upgrade, faster RAM)
7.6 TiB  0.8 TiB  24 Hrs  711k  25 GiB  15 Days   99%   24 TBW
14.6TiB  1.8 TiB  48 Hrs  710k  23 GiB  14 Days   99%   23 TBW
8.1 TiB  1.3 TiB  26 Hrs  709k  27 GiB  12 Days   99%   21 TBW
7.2 TiB  1.3 TiB  24 Hrs  707k  23 GiB  11 Days   99%   20 TBW
5.9 TiB  1.0 TiB  24 Hrs  706k  18 GiB  10 Days   99%   18 TBW
7.2 TiB  1.3 TiB  24 Hrs  704k  18 GiB   9 Days   99%   17 TBW
8.8 TiB  1.3 TiB  24 Hrs  702k  19 GiB   8 Days   99%   15 TBW
5.9 TiB  1.2 TiB  24 Hrs  701k  18 GiB   7 Days   99%   14 TBW
7.6 TiB  1.3 TiB  19 Hrs                 6 Days  100%   13 TBW
7.0 TiB  1.1 TiB  27 Hrs                 5 Days  100%   11 TBW

Update: Forgot to mention I've only ever used mongod v6.0.0.

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

1 participant