Getting out of memory error with entering too high numbers in article caching

[tf]

Specs: Intel i7700k 4,2GHz, 16GB Ram.

System drive: Intel NMVe 600P 512GB drive
Temp disk for Alt.Binz: Samsung NMVe 970 EVO Plus 500GB drive
Final disk for downloads: Seagate 4TB 7200 RPM SATA 600

Internet connection: 1Gbit/1Gbit on 1Gbit NIC

Alt.Binz version: 0.47.2.2

When I download from usenet in Alt.Binz and the filesize is like 3-400MB (or larger), my download speeds seems to go from 110MB/s to about 50-70MB/s. I found this to be odd. Previously I had my temp dir set on my system drive, and it never really went below 100MB/s, even though it was being pushed more. So I tried checking the download settings in Alt.Binz. Article caching was set to 500MB. I tried setting it to 2000MB. Then it seemed to work fine. I got max speed. But only for a while. Then Alt.Binz freeze up and eventually gives me an out of memory error.

Odd, since I wasn't really running anything memory intensive. I tried monitoring my memory usage and I never really exceeded like 8-9 GB of usage. Even with the 2000MB setting in Alt.Binz, it rarely used more than 1-1.3 GB.

I've tried entering smaller amounts in the article caching entry, but seems like when it's as high as it needs to maintain full speed, it runs out of memory and if I set it low enough to not run out of memory, I get half speed.

Anyone have experience in this field?

Kindest regards a long time user
jacobtf

[Rdl]

Alt.Binz is 32bit program. That means it can allocate up to 2GB of memory (I won't go into explanation about LAA version)
Setting cache size to 2GB is terible idea cause it leaves nothing for the rest of the program.

Here's an idea for you to test: Make ramdisk as drive with few gigabytes and in altbinz set temp folder to new ramdrive and disable cache option in altbinz. See if that helps.

http://www.ltr-data.se/opencode.html/#ImDisk

[tf]

Okay so I installed the RAM disk, setup the temp dir in alt.binz to the drive (R for RAM, hah) and the cache to 0 (which I presume disables it).

Speed was the same, but it froze alt.binz after just 20-30 seconds and I had to force shutdown.

So I went back to using my NVMe drive. I've tried setting cache to anything from zero to 2000 MB. Zero gives the same result as 1000MB. As soon as I set it at like 1500-2000, the speed doubles for about a few minutes, then it freezes (alt.binz). I thought the NMVe drive was getting too hot, but it's at 53 degrees celcius. That's nothing!

The odd thing is that when I used my system drive as temp dir, the speed is fine. 100MB+ per second.

Alright, so maybe one drive is slower than the other? But the Samsung 970 should be vastly faster when I read comparisons!

Next up, maybe one NMVe slot is faster than the other. But how come I can download at max speed for a few minutes sometimes, before it just freeze?

To compare, I've tried downloading large amounts of data to my google drive to the Samsung 970, and I can sustain 100MB/s for hours on end. Uploads go full speed too. I really don't know, what's going on.

I can't really see my ram being faulty either. I use the computer for video editing in DaVinci Resolve, I play intensive games etc. I very, very rarely have anything crash on my setup, and to be honest, it's only been in the past few days that alt.binz have frozen up on me.

Am I out of luck here?

[Rdl]

Maybe it's about write strategy for one drive compared to the other. Maybe samsung is declared as removable drive...