On Oct 14, 2010, at 10:13 AM, William Siegrist wrote:
On Oct 14, 2010, at 9:27 AM, William Siegrist wrote:
I am in the process of moving buildbot onto faster storage which should help
with performance. However, during the move, performance will be even worse
due to the extra i/o. There will be a downtime period in the next few days
to do the final switchover, but I won't know when that will be until the
preliminary copying is done. I am trying not to kill the master completely,
but there have been some slave disconnects due to the load already this
morning. I'll let everyone know when the downtime will be once I know.
The copying of data will take days at the rate we're going, and the server is
exhibiting some strange memory paging in the process. I am going to reboot
the server and try copying with the buildbot master down. The master will be
down for about 15m, if I can't get the copy done in that time I will schedule
a longer downtime at a better time. Sorry for the churn.
Most of build.webkit.org is now running on the newer/faster storage. However,
the results data[1] is hundreds of gigabytes, going back 6 months, and the new
storage is not big enough. Does anyone have any opinion on how much data to
keep in results? Does anyone ever look back more than a month or two? For now,
the results will still come up a slowly, but hopefully the rest of buildbot is
a little more responsive. We're still planning to move all of webkit.org to
better hardware soon, but we hit some delays in that process.
[1] http://build.webkit.org/results/
Thanks
-Bill
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
