From: Brian B. <bri...@gm...> - 2011-10-14 16:06:07
|
My personal take is that this is not an excuse to resist adjusting the 32 GB limit. Besides the fact that the actual usage of valgrind (vs downloads) is likely going to be more skewed toward developer machines and environments, it should make sense to make valgrind as robust to memory usage as possible. On the other hand, I can completely understand the resistance if the feature is hard to implement, and weighing the difficulty vs common usage cases. Anyone care to explain the fundamental limitation to 32 GB? What kind of work would be required to increase that by some number of binary orders of magnitude? Thanks, Brian On Fri, Oct 14, 2011 at 8:54 AM, John Reiser <jr...@bi...> wrote: > On 10/14/2011 08:01 AM, Yeshurun, Meir wrote: >> 1. How do you know that? > > By the statistics on downloads of valgrind (as adjusted for typical > multiple-installs-from-one-download), by the statistics on > median {,S}DRAM in x86* machines of any kind (still < 4GB), > by the limits on memory controller drive and DRAM die density > (16GB in a common box < $1000 or so), and by traveling around. > >> 2. They are going to become increasingly common > > In absolute numbers, yes. But in the next five years > the percentage still will be less than 1%. > (Even discounting the fact that "smartphones" are > full-fledged computers in every way, already vastly > outnumber x86* machines of all kinds, and will take > a while to exceed even 1GB DRAM.) > > -- > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > |