-
Notifications
You must be signed in to change notification settings - Fork 4
Memory usage #48
Comments
Can you test the new version |
thread 'main' panicked at 'called Obviously I can provide you the file somewhere! |
Was your scan above ~4.2GHz? |
6GHz ;) |
fedab33 should fix it. Can you test the latest |
The file is to big for transfer.sh. How would I do the cargo thing far master? |
Transfer.sh should handle up to 10GB. Or mega.nz for up to 50GB, but you need to create an account. If you're using |
I am trying to visualize a 6GB file (1.6GB gzip-compressed) that was generated by a hackrf_sweep. Surely the python code was limited to single threading (and I didn't see a rendering yet) this application instantly captures all my RAM (16GB) but does seem to have multicore performance, but I fail to see why this RAM usage is justifiable. The CSV file is an ASCII representation of "floats". But actually the depth of the values can be represented in only two bytes per value. Could you put some effort towards a better RAM ratio?
The text was updated successfully, but these errors were encountered: