Issue 2500: Have our own contig implementation http://code.google.com/p/chromium/issues/detail?id=2500
New issue report by [EMAIL PROTECTED]: Regarding bug http://code.google.com/p/chromium/issues/detail?id=265 Issue: The way the file 'User Data\Safe Browsing' is extended on Windows leads it to being quite fragmented. On systems with slow disk seek times, low free disk space or already highly fragmented drive, the whole system performance hit can be quite important. Fix: - Implement the algorithm discussed in http://msdn.microsoft.com/en-us/library/aa363911(VS.85).aspx - This could be used for disk cache too. Caveats: - The algorithm to fix this is relatively sensitive. Badly implemented, it can cause more harm than good. - This shouldn't not be done on flash-based drives. Maybe measuring the seek time could help detect and skip these drives. - This requires administrative privilege. On restricted user account, this would not be executed. Note that this is the default on Vista with UAC enabled but Vista has by default a defragmentation scheduled every 3 weeks. Issue attributes: Status: Available Owner: [EMAIL PROTECTED] CC: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Labels: Type-Feature Pri-3 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 -~----------~----~----~----~------~----~------~--~---
