g6k icon indicating copy to clipboard operation
g6k copied to clipboard
verified publisher icon fplll

Crashes with full_sieve.py

Open joerowell opened this issue 5 years ago • 1 comments

When running ./full_sieve.py 130 --threads 24 on a machine with 32GB of RAM and 24 cores, I get a crash. The reason for this is that the Siever attempts to reserve the amount of RAM it would need to sieve in dimension 130 during construction - which clearly I don't have (>256 GB would be needed).

However, perhaps bizarrely, the siever then relinquishes this memory when the workout begins. This seems undesirable: perhaps we could just issue an error instead.

joerowell avatar Dec 09 '20 10:12 joerowell

Oh, sorry for the delay, I missed that. It's probably solved by now, but there is a hardcoded maxdim (set to 128 IIRC) at compile time. You can adjust this during rebuild.sh with the option -m|--maxsievingdim.

Can you confirm this solves it ?

lducas avatar Apr 26 '21 16:04 lducas