-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, Jun 26, 2015 at 11:33:48AM +0200, Dan wrote:
> Yes the calculation is memory/cpu instensive. I can not consider a > faster (multi-core) processor because I do not have the budget to buy > a new machine. But I need more RAM, the calculation do not fit in 64 > GB of RAM. In that case, if the computer has to resort to disk (swap), most probably more RAM might help. How is the access pattern? Does the calculation need access to "all of its address space" "all of the time"? In that case, there seems you have no choice. OTOH this will be the pessimal access pattern wrt memory caches (which will be stretched half as thinly with the more RAM), but probably you know all of that. > Probably I will increase the RAM, I will also compare the calculation > time. I will post the results in the list. Looking forward to your results. Thanks! - -- t -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlWNH2wACgkQBcgs9XrR2kab0gCcDT6HRfv8VtW82Xvj4wEhTv9w B88AnR3m/LkRqg+nTQsNmsvzUA/wtVfA =8/EZ -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150626094620.ga11...@tuxteam.de
