RunOnProcessorExplicitly ... la soluzione alle incompabilità con dualcore
Salve a tutti ...
Dopo giorni di ricerche e prove ho trovato questo : RunOnProcessorExplicitly
cos'è ??? il modo per avviare un test o una applicazione/gioco con un singolo core specifico
(che dovremmo noi specificare), senza ogni volta entrare nei processi della task di windows per
dare l'affinità del core al prog che ci interessa .... un modo + veloce e pratico ....
Ho fatto diverse foto per dimostrare che ROPE funziona davvero e infine una info su come usarlo.
Ottimo anche per quei giochi che in dual-core danno un sacco di problemi ...
tipo Colin Mcrae 4 / 5 , Painkiller e forse altri che al momento non ho potuto provare ...
E' semplice da installare e si può usare all'interno di un collegamento o di un file .bat
Di seguito ho voluto riportare ( in inglese ... sigh ! ) tutte le info sul programma e sul
produttore ( il programa è freeware e publicizzato direttamente sul forum AMD ) :
RunOnProcessorExplicitly
Aka ROPE
A Systems Management Utility to allow applications and services to execute
on specifically defined processor(s) in a SMP environment, when running
under Microsoft® Windows NT 4.0/2000/XP.
Introduction
Today symmetric multiprocessor (SMP) is by far the most popular parallel hardware architecture, with
the Fujitsu Siemens® Primergy Series offering up to 8 processors and the Unisys® ES7000 Server
with up to 32 processors. However the ability of many applications to be able to scale over multiple
processors is still a challenge. To overcome this problem RunOnProcessorExplicitly (ROPE) has
been written to utilize the available resources. ROPE is a Systems Management Utility (SMU) will
allow the user to specify which processor(s) that applications and or services will be allowed to run
on. The number of processors can be defined from 1 up to the maximum number of online
processors; automatic processor load balancing is also a feature of this SMU.
ROPE Features
The application / service can be targeted to processor(s) in one of the following 2 ways, with
Processor Load Balancing via the –p option, or the –f option which forces the application / service
onto the specified processor(s). Setting a target processor(s) also restricts any other processes
created by the application / service to be executed on the same processor(s). Processor numbering
starts at 0, on a 4-way processor the valid processor numbers are 0, 1, 2 & 3.
Minimum and Maximum Working Set Size can also be specified in K values. This is done via the -m
option. Minimum Working Set Size Specifies a minimum working set size for the process. The virtual
memory manager attempts to keep at least this much memory resident in the process whenever the
process is active. Maximum Working Set Size specifies a maximum working set size for the process.
The virtual memory manager attempts to keep no more than this much memory resident in the
process whenever the process is active and memory is in short supply. If only a single value is
specified on the -m option both Minimum Working Set Size and Maximum Working Set Size are set to
the same value. However it is worth noting that if Minimum Working Set Size and Maximum Working
Set Size have the value 0xffffffff, the function temporarily trims the working set of the specified
process to zero. This essentially swaps the process out of physical RAM memory, not a good choice
to make.
Working Set Size
The operating system allocates working set sizes on a first-come, first-served basis. For example, if
an application successfully sets 40 megabytes as its minimum working set size on a 64-megabyte
system, and a second application requests a 40-megabyte working set size, the operating system
denies the second application's request. Setting an application's minimum and maximum working set
sizes does not guarantee that the requested memory will be reserved, or that it will remain resident at
all times. When the application is idle, or a low-memory situation causes a demand for memory, the
operating system can reduce the application's working set. When you increase the working set size of
an application, you are taking away physical memory from the rest of the system. This can degrade
the performance of other applications and the system as a whole. It can also lead to failures of
operations that require physical memory to be present; for example, creating processes, threads, and
kernel pool. Thus, you must use the option (-m) carefully.
ROPE Command Format
Format of ROPE command is as follows,
ROPE -f <specific processors>| -p <number of processor> -x <minmem, maxmex>
-n <program to execute>
Where -f the actual processor numbers on which to run the task
e.g. -f 2-4 or -f 0,3,7
-p the number of processors to use for this task
e.g. -p 3 note this implies load balancing
-m the minimum working set size in K, maximum working set size in K
e.g. -m 32,64 or -m 96
-n the fully qualified program name to execute, along
with any parameters required for the executing task.
e.g. -n h:\Ostar\bin\hrncr.exe log
-q generates a product number to request a License Key. No program execution takes
place
Note: commas and hyphens are required delimiters.
link for download : http://shareware.pcmag.com/product.p...SiteID%5Dpcmag
di seguito degli screen su come funziona e come bisogna usarlo :
.
.
.
.
.
.
spero di essere stato di aiuto a molti che , come me , hanno cercato per molti giorni un
semplice programma o comando per usare ogni singolo core in modo indipendente ...
soprattutto nei test per valutare la vera stabilità di ogni singolo core .
Rispondi quotando
