Issue 2499: Throttle the safe browsing I/O http://code.google.com/p/chromium/issues/detail?id=2499
New issue report by [EMAIL PROTECTED]: Regarding bug http://code.google.com/p/chromium/issues/detail?id=265 On XP, the thread's priority has very little impact when doing I/O, i.e. the whole system will still suffer. The only way to throttle this is either to call PlatformThread::YieldCurrentThread() or to use THREAD_PRIORITY_IDLE. Idle level has impact on the I/O since the thread won't be immediately scheduled for execution even if a core is in the idle state, thus creating a form of throttling alas YieldCurrentThread. Microsoft fixed that on Vista with the THREAD_MODE_BACKGROUND_BEGIN flag which has true effect on I/O throttling. This feature request is about implementing both in the SafeBrowsingService::db_thread_. Issue attributes: Status: Available Owner: [EMAIL PROTECTED] CC: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Labels: Type-Feature Pri-2 OS-Windows Area-BrowserBackend Performance Usability -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" 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-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
