-
Data: 2011-10-08 05:31:34
Temat: Re: koszt zarzadzania
Od: " " <f...@g...SKASUJ-TO.pl> szukaj wiadomości tego autora
[ pokaż wszystkie nagłówki ]M.M. <m...@t...pl> napisał(a):
> > <f...@g...SKASUJ-TO.pl> napisał(a):
>
>
> > (o ile rozumiem) fokusowany proces ma jakiegos boosta
> Ma na pewno, wiele razy to obserwowałem. Nie mam pewności
> skąd to się bierze, strzelam że z ustawień w systemie,
> czy optymalizować usługi w tle.
>
> Pozdrawiam
z tego co pisze w windows internals w xp (a mam stare wydanie tak ze nie
wiem jak w ciscie i 7) wotki procesu w foreground dostaja 60 milisekundowe
slice zamiast 20 ms (jak ustawic w zakladce te bacground services) to
jak rozumiem tego boosta nie ma i wszystkie procesy dostaja po 120 ms
Quantum Boosting
Prior to Windows NT 4.0, when a window was brought into the foreground on a
workstation or client system, all the threads in the foreground process (the
process that owns the thread that owns the window that's in focus) received a
priority boost of 2. This priority boost remained in effect while any thread
in the process owned the foreground window. The problem with this approach
was that if you started a long-running, CPU-intensive process (such as a
spreadsheet recalculation) and then switched to another CPU-intensive process
(such as a computer-aided design tool, graphics editor, or a game), the
process now running in the background would get little or no CPU time because
the foreground process would have its threads boosted by 2 (assuming the base
priority of the threads in both processes are the same) while it remained in
the foreground.
This default behavior was changed as of Windows NT 4.0 Workstation to instead
triple the quantum of the threads in the foreground process. Thus, threads in
the foreground process run with a quantum of 6 clock ticks, whereas threads
in other processes have the default workstation quantum of 2 clock ticks. In
this way, when you switch away from a CPU-intensive process, the new
foreground process will get proportionally more of the CPU, because when its
threads run they will have a longer turn that background threads (again,
assuming the thread priorities are the same in both the foreground and
background processes).
Note that this adjustment of quantums applies only to processes with a
priority higher than Idle on systems configured to Programs (or Applications,
in Windows 2000) in the Performance Options settings described in the
previous section. Thread quantums are not changed for the foreground process
on systems configured to Background Services (the default on Windows Server
systems).
--
Wysłano z serwisu Usenet w portalu Gazeta.pl -> http://www.gazeta.pl/usenet/
Następne wpisy z tego wątku
- 08.10.11 05:51
- 08.10.11 06:03
- 08.10.11 08:51
- 08.10.11 20:47 M.M.
Najnowsze wątki z tej grupy
- Arch. Prog. Nieuprzywilejowanych w pełnej wer. na nowej s. WWW energokod.pl
- 7. Raport Totaliztyczny: Sprawa Qt Group wer. 424
- TCL - problem z escape ostatniego \ w nawiasach {}
- Nauka i Praca Programisty C++ w III Rzeczy (pospolitej)
- testy-wyd-sort - Podsumowanie
- Tworzenie Programów Nieuprzywilejowanych Opartych Na Wtyczkach
- Do czego nadaje się QDockWidget z bibl. Qt?
- Bibl. Qt jest sztucznie ograniczona - jest nieprzydatna do celów komercyjnych
- Co sciaga kretynow
- AEiC 2024 - Ada-Europe conference - Deadlines Approaching
- Jakie są dobre zasady programowania programów opartych na wtyczkach?
- sprawdzanie słów kluczowych dot. zła
- Re: W czym sie teraz pisze programy??
- Re: (PDF) Surgical Pathology of Non-neoplastic Gastrointestinal Diseases by Lizhi Zhang
- CfC 28th Ada-Europe Int. Conf. Reliable Software Technologies
Najnowsze wątki
- 2024-12-30 Moduł BT BLE 5.0
- 2024-12-30 Łódź => Application Security Engineer <=
- 2024-12-30 Lublin => Inżynier bezpieczeństwa aplikacji <=
- 2024-12-30 Nowy Outlander PHEV w PL
- 2024-12-30 Warszawa => Key Account Manager <=
- 2024-12-30 Katowice => Key Account Manager (ERP) <=
- 2024-12-28 Śmiechu KOOOOOOPA ;-)
- 2024-12-29 Pomiar amplitudy w zegarku mechanicznym
- 2024-12-28 Antyradar
- 2024-12-28 Deweloper przegral w sadzie musi zwrócic pieniądze Posypia sie kolejne pozwy?
- 2024-12-28 Warszawa => Full Stack .Net Engineer <=
- 2024-12-28 Warszawa => Sales Assistant <=
- 2024-12-28 Warszawa => Programista Full Stack .Net <=
- 2024-12-28 Warszawa => Full Stack web developer (obszar .Net Core, Angular6+) <=
- 2024-12-28 Katowice => Head of Virtualization Platform Management and Operating S