search for: small_memory

Displaying 4 results from an estimated 4 matches for "small_memory".

Did you mean: all_memory
2015 Jan 18
2
default min-v/nsize parameters
...ch the current numbers are optimal. The current minimum size increases for node and vector heaps are 40KB and 80KB respectively. This grows as the heap grows (min + .05 * heap), but still means that we do many more expensive garbage collections at while growing than we need to. Paradoxically, the SMALL_MEMORY compile option (which is suggestd for computers with up to 32MB of RAM) has slightly larger at 50KB and 100KB. I think we'd get significant benefit for most users by being less conservative about memory consumption. The exact sizes should be discussed, but with RAM costing about $10/GB it d...
2015 Jan 20
1
default min-v/nsize parameters
...imum size >> increases for node and vector heaps are 40KB and 80KB respectively. >> This grows as the heap grows (min + .05 * heap), but still means that >> we do many more expensive garbage collections at while growing than we >> need to. Paradoxically, the SMALL_MEMORY compile option (which is >> suggestd for computers with up to 32MB of RAM) has slightly larger at >> 50KB and 100KB. >> >> I think we'd get significant benefit for most users by being less >> conservative about memory consumption. The exact...
2015 Jan 19
0
default min-v/nsize parameters
...rs are optimal. The current minimum size > increases for node and vector heaps are 40KB and 80KB respectively. > This grows as the heap grows (min + .05 * heap), but still means that > we do many more expensive garbage collections at while growing than we > need to. Paradoxically, the SMALL_MEMORY compile option (which is > suggestd for computers with up to 32MB of RAM) has slightly larger at > 50KB and 100KB. > > I think we'd get significant benefit for most users by being less > conservative about memory consumption. The exact sizes should be > discussed, but with...
2015 Jan 15
2
default min-v/nsize parameters
Just wanted to start a discussion on whether R could ship with more appropriate GC parameters. Right now, loading the recommended package Matrix leads to: > library(Matrix) > gc() used (Mb) gc trigger (Mb) max used (Mb) Ncells 1076796 57.6 1368491 73.1 1198505 64.1 Vcells 1671329 12.8 2685683 20.5 1932418 14.8 Results may vary, but here R needed 64MB of N cells and 15MB