Huge RAM use

[douweschulte]

In GitLab by @nonnominandus on Mar 4, 2020, 11:04

The assembler seems to use a lot of ram (up to ~2Gb), I guess this is while generating the report in memory, maybe it would be nice to stream this report to the file instead of buffering it all the time.

[douweschulte]

In GitLab by @nonnominandus on Mar 25, 2020, 19:04

After some test with dotMemory it was clear that the memory usage is not unreasonable. And that it uses so much because my computers have much RAM, so the GC is called later.

By Douwe Schulte on 2020-03-25T18:04:03 (imported from GitLab)

[douweschulte]

In GitLab by @nonnominandus on Mar 9, 2020, 12:10

While running a very long peaks dataset in the recombination step. It was visible that after running at 100% for a time the CPU usage did go down to ~60% and the RAM usage increased from ~400MB to ~950MB while the CPU usage increased again to 100%. It very slightly increased RAM usage for a time (~20MB) and then at once got back to ~600MB. After this it slowly climbed to ~750MB. It kept here for a long while after which it got back to ~35% CPU and immediately 100% then back to 60% then hovering around 90% while the RAM usage was jumping between ~750MB and ~1200MB.

In the Report generation (without contigs and reads) it got to max ~6000MB but continuously jumped up and down to ~2000MB and around 3500MB.

After this it crashed, sadly.

ERROR: The length cannot be greater than the capacity.
Parameter name: valueCount

(It crashed because some HTML string was bigger than 1 GB)

By Douwe Schulte on 2020-03-09T14:25:00 (imported from GitLab)

[douweschulte]

In GitLab by @nonnominandus on Mar 25, 2020, 19:04

closed

By Douwe Schulte on 2020-03-25T18:04:03 (imported from GitLab)