Turning off auto refresh by default sounds reasonable idea right now... with
an option to enable it if really desired... &autorefresh[=<n>] where n is a
number of minutes maybe (defaults to 1) type thing.
A fair amount of the load may just evaporate with that change.
On Tue, Jul 14, 2009 at 3:32 PM, Jeremy Orlow <jor...@google.com> wrote:
> On Tue, Jul 14, 2009 at 2:42 PM, Adam Langley <a...@chromium.org> wrote:
>
>>
>> On Tue, Jul 14, 2009 at 2:40 PM, Albert J. Wong
>> (王重傑)<ajw...@chromium.org> wrote:
>> > That is pretty nuts. Is it calling fsync or something crazy? Since you
>> > said strace, I'm assmuming linux. In that case, the buffer cache should
>> be
>> > saving you from disk accesses for most everything.
>>
>> Of course, vmstat 1 will tell you what disk IO is happening. If you
>> don't have noatime, that would probably be good.
>
>
> atop is a really nice program for getting a birds eye view of what's going
> on with the system. It's not installed by default, but if you're running
> ubuntu, it's easy to install.
>
>
> More generally: I think there are a couple uses of the build bots:
> 1) Most people just want to know "can I commit" and then are watching one
> specific CL's status. In this case, not auto-refreshing is fine and not
> much history is fine.
> 2) Sheriffing is the one case where I think you actually do need
> auto-refreshing, but normally you don't need a lot of history. That said,
> sometimes things fail and then....
> 3) You're trying to fix things: In this case you want to see a lot of
> history (or at least need the option to see more) and you do NOT want it to
> auto refresh. I've definitely had times when I wish there was a "show me
> more" button. And I've definitely have been reading something far down the
> page only to have it refresh on me.
>
> It seems to me that these requirements are diverse enough that one single
> configuration isn't going to make everyone happy. I know you can do a bunch
> of customization so you can see exactly what you want, but I assume that
> will only chew up more resources. Maybe the right way to go is a couple
> customized pages for each roll? There's definitely much more information
> there than people need most of the time, though.
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
