1

Topic: I am surprised

I did not write for a long time already real drivers for . But I remember that a good form was considered not to select the big pieces of storage, especially nonpaged. Also what I see in fresh  refs - selection 16 NonPagedPoolNx?.text:FFFFF803412875DC loc_FFFFF803412875DC:; CODE XREF: MlLogScanLog+A4j.text:FFFFF803412875DC mov ebx, 1000000h.text:FFFFF803412875E1 mov r8d, 6C6C534Dh; Tag.text:FFFFF803412875E7 mov edx, ebx; NumberOfBytes.text:FFFFF803412875E9 mov ecx, 200h; PoolType.text:FFFFF803412875EE call cs: __ imp_ExAllocatePoolWithTag.text:FFFFF803412875F4 mov r14, rax.text:FFFFF803412875F7 test rax, rax.text:FFFFF803412875FA jnz short loc_FFFFF80341287606.text:FFFFF803412875FC mov edi, 0C000009Ah.text:FFFFF80341287601 jmp loc_FFFFF803412876B6 So to say FYI

2

Re: I am surprised

Hello, MShura, you wrote: MS> I remember that a good form was considered not to select the big pieces of storage, especially nonpaged. It is Enough to look at the memory size occupied with kernels and system in the eights-tens not to be surprised any more to such tendencies.

3

Re: I am surprised

MS> Also what I see in fresh  refs - selection 16 NonPagedPoolNx?. And when that at me NT4 with NTFS tolerably turned with 16 RAM.

4

Re: I am surprised

Hello, ononim, you wrote: O>. And when that at me NT4 with NTFS tolerably turned with 16 RAM. I had once a good time  different systems in . 2k it was possible to knead before tolerable operation on 64-96 a MB, XP - 128-192, Vista/Win7 - 384, Win8 - 512, and Win10 and on gigabyte itself cannot service. It is visible that fast growth began with 6.x, and before was quite linear.

5

Re: I am surprised

Hello, MShura, you wrote: MS> Also what I see in fresh  refs - selection 16 NonPagedPoolNx? Anything strange, refs - server fs for the big sizes of disks. Probably these 16 are necessary to it for what-thread  for normal rapid access. Taking into account that on servers 16+ storages - all apprx.

6

Re: I am surprised

7

Re: I am surprised

Hello, Evgenie Muzychenko, you wrote: I eat> Hello, ononim, you wrote: O>>. And when that at me NT4 with NTFS tolerably turned with 16 RAM. I eat> once had a good time  different systems in . 2k it was possible to knead before tolerable operation on 64-96 a MB, XP - 128-192, Vista/Win7 - 384, Win8 - 512, and Win10 and on gigabyte itself cannot service. It is visible that fast growth began with 6.x, and before was quite linear.  please as you win 8 kneaded, the general principles

8

Re: I am surprised

Hello, sergey2b, you wrote: S> as you win 8 kneaded, the general principles the General principles  are identical to all: to disconnect unnecessary in Features (which in Programs and Features) to disconnect any indexings, System Restore, Remote Assistense, Remote Desktop and other that is controlled by a human way, then to open the list of services and to disconnect/forbid unnecessary, only not to forget to fix their starting state that in case of problems not to forget what initially did not work and what you disconnected. Switch-off of visual effects (except unless, "live" drag and drop of windows) especially does not influence occupied storage, but noticeably lifts high-speed performance on not the fastest iron. And switch-off of animation of windows occasionally allows to get rid of sound/video stutters.