I was using the original .27 release and on upgrading to .29 I found the disk thrashing too intense for my liking. I know I can disable the malware phishing thing to reduce this but would rather have that functionality. So I searched out a build of Chromium and after some some trial and error settled on build 1835 which is working wonderfully with low disk thrashing.
Then I read this and reinstalled Chrome and updated to the dev channel build. I launched it with the new http and wm options --new-http -- magic_browzR and am seeing similar levels of disk thrashing, slightly higher, to Chromium build 1835 which is good. However the one thing I noticed is CPU spiking to 20-30 percent on this dev centre 0.2.152.1 build with these new options enabled when performing simple tasks like opening a new link or loading a page. It inevitably goes to 20% plus. This level of CPU usage immediately goes down when launching without the http and wm options. This cpu spike is quite transparent with enabling and disabling the new options. Is anyone else seeing this? Raul On Sep 17, 5:16 am, "Pam Greene" <[EMAIL PROTECTED]> wrote: > Chromium nightly builds don't exist yet. :) > > If you're talking about downloading an arbitrary snapshot from the > continuous builders, the difference is that the ones sent on the dev > channel have had some testing and QA. They're not as thoroughly > examined as a release build, but far more than the snapshots. A > snapshot may not even have passed the automated tests, much less > anything else. We really don't recommend that you run > continuous-build snapshots. > > Oh, and the snapshots are Chromium, whereas the dev channel is Google Chrome. > > - Pam > > On Tue, Sep 16, 2008 at 4:27 PM, rig <[EMAIL PROTECTED]> wrote: > > > What is difference between chrome dev channel and chromium nightly > > builds? > > > Thank you > > > On Sep 16, 1:32 am, Mark Larson <[EMAIL PROTECTED]> wrote: > >> Google Chrome now provides a way for people to get early access releases > >> automatically: the Dev channel. > > >> The Dev channel lets you test the latest fixes and get access to new > >> features as they're being developed. We will release new builds to the Dev > >> channel about every week so that you can preview --and provide feedback > >> on-- > >> what's coming in Google Chrome. > > >> If you want an easy way to help make Google Chrome better, want to test new > >> changes with your website before they're released generally, or just like > >> being on the bleeding edge, please sign up for the Dev channel. > > >> You can learn more about the Dev channel and how to subscribe > >> here:http://dev.chromium.org/getting-involved/dev-channel/ > > >> We just released 0.2.152.1 to the Dev channel. The release notes are > >> here:http://sites.google.com/a/chromium.org/dev/getting-involved/dev-chann... > > >> If you have any questions, please send them directly to me (so I can > >> compile > >> the FAQ). > > >> Thanks, > >> Mark Larson > >> Google Chrome Program Manager --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
