Jason Merrill <ja...@redhat.com>:
> > What do your repo load times look like, and how much RAM is in your
> > surgery machine? My loads are currently hanging in D state after 13 hours
> > on
> > a 64GiB hexacore Xeon 3 running at nominally 3.50GHz. I'm beginning
> > to wonder if I have some kind of high-memory error - I don't recall this
> > happening last time I took a swing at the conversion.
>
> I think it was on the order of 18-20 hours, but it's been a while.
> The machine I was using before actually has more memory now than it
> did then; free -g reports 251G total memory.
OK, your figures make sense - I designed the Great Beast around
getting high memory bandwidth in the expectation that working sets
from large conversions would be huge.
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
My work is funded by the Internet Civil Engineering Institute: https://icei.org
Please visit their site and donate: the civilization you save might be your own.
