When commenting your switch, please use the same voice as surrounding comments. Can't find the switch you are looking for? Try looking in: ash/constants/ash_ base/base_ etc. However, having a valid prefetch argument for these process types is required to prevent them from interfering with the prefetch profile of the browser process. It is likely that the prefetcher won't work for these process types as it won't be able to observe consistent file reads across launches. prefetch:# argument shared by all process types that don't have their own. Use profiles 5, 6 and 7 as documented on kPrefetchArgument* in content_. prefetch:# arguments for the browser process launched in background mode and for the watcher process. Note: # must always be in otherwise it is ignored by the Windows prefetcher. Note that the browser process has no /prefetch:# argument as such all other processes must have one in order to avoid polluting its profile. Because reads depend on the process type, the prefetcher wouldn't be able to observe consistent reads if no /prefetch:# arguments were used. It has been observed that when file reads are consistent for 3 process launches with the same /prefetch:# argument, the Windows prefetcher starts issuing reads in batch at process launch.
prefetch:# arguments to use when launching various process types. This page lists the available switches including their conditions and descriptions. Some change behavior of features, others areĭebugging or experimenting. There are lots of command lines which can be used with the Google Chrome browser.
0 kommentar(er)
