Anton Korobeynikov
Anton Korobeynikov
More information about that std::bad_alloc – it seems mesh failed to fulfill request to allocate 28 Gb as one piece. And indeed, in ``` void *GlobalHeap::malloc(size_t sz) { ``` We're...
Thanks for clarification. This effectively closes Mesh for SPAdes as we're routinely allocating more than 64 Gb of RAM. Apparently no other memory allocator we are aware of has such...
As much as necessary. Could allocate 0.5 Tb, could allocate 1 Tb. It depends on the input.
It might be 100 Mb, it might be 4 Gb, it might consume 1 Tb. Everything depends on the input.
Well, for us we'd need something like a run-time constant then. E.g. the user could specify max amount of memory he / she could use.
@bpowers So, I tried again on small dataset (with expected memory consumption less than 10 Gb). Unfortunately, I had to lower kMeshesPerMap down to 0.1, otherwise it did not work....
@dumblob The project seems to be abandoned. We (SPAdes) are using mimalloc now.
@paoloczi I just double checked and it seems that `--minnodlen 88` case is working now (after https://github.com/asl/BandageNG/pull/128)
@paoloshasta The snapshots are posted at https://github.com/asl/BandageNG/releases as "pre-releases". As soon as they are built which takes some time.
@paoloshasta It was just built: https://github.com/asl/BandageNG/releases/tag/continuous