Radare2: use all cores in /sys/install.sh (make -j 8 for example)

[condret]

i don't do shellscripts very often, so i'm not sure if this is possible.

[XVilka]

probably determine it on the fly with

grep -c "processor" /proc/cpuinfo

command, that's only for Linux though...

[condret]

i now how you can determine the number of cores in windows, but only in c

[crowell]

Also nproc
On Oct 21, 2015 7:13 PM, "condret" [email protected] wrote:

i now how you can determine the number of cores in windows, but only in c

—
Reply to this email directly or view it on GitHub
https://github.com/radare/radare2/issues/3536#issuecomment-149965684.

[jvoisin]

Just use make -j

[jjdredd]

If the  -j  option  is given without an argument, make will not limit
the number of jobs that can run simultaneously.

Sounds overkillish and oomish.

[crowell]

No this is a terrible idea make -j can bring your system to a halt
On Oct 21, 2015 7:27 PM, "jvoisin" [email protected] wrote:

Just use make -j

—
Reply to this email directly or view it on GitHub
https://github.com/radare/radare2/issues/3536#issuecomment-149966846.

[crowell]

make -j $(nproc+1) is usually what it recommended.
On Oct 21, 2015 7:34 PM, "Judge_Dredd" [email protected] wrote:

If the -j option is given without an argument, make will not limit
the number of jobs that can run simultaneously.

Sounds overkillish and oomish.

—
Reply to this email directly or view it on GitHub
https://github.com/radare/radare2/issues/3536#issuecomment-149971504.

[CoolOppo]

you mean make -j $(nproc)+1 right? or am i wrongo

[radare]

This is already done

On 21 Oct 2015, at 19:10, Anton Kochkov [email protected] wrote:

probably determine it on the fly with

grep -c "processor" /proc/cpuinfo
command, that's only for Linux though...

—
Reply to this email directly or view it on GitHub.

[radare]

The nproc+1 rule is like swap=ram_2 rule. Both were invented when the pentium pro ruled the world. Nowadays it makes no sense to follow those rules. Mainly because almost every processor have 2 cores, so you end up having to do nproc_2.. But thats not true for arm, etc etc. so as long as every arch performs different is better to keep a sane value like the current hardcoded -j8

On 21 Oct 2015, at 19:56, CoolOppo [email protected] wrote:

you mean make -j $(nproc)+1 right? or am i wrongo

—
Reply to this email directly or view it on GitHub.

[radare]

You can fix this with hardware

On 21 Oct 2015, at 19:33, Jeffrey Crowell [email protected] wrote:

No this is a terrible idea make -j can bring your system to a halt
On Oct 21, 2015 7:27 PM, "jvoisin" [email protected] wrote:

Just use make -j

—
Reply to this email directly or view it on GitHub
https://github.com/radare/radare2/issues/3536#issuecomment-149966846.

—
Reply to this email directly or view it on GitHub.

[radare]

About how to get the amlunt of cpus is something useless. As explained in my prev reply. Every os provides this info different. And each cpu model and arch responds diferent. And the build system also, doesnt paralelixes in all situations because there are some blocker steps that halt that performance a bit.

Do not try to mess with c code to determine the number of cpus. Just use MAKE_JOBS or use the default -j8 provided by sys/build.sh

On 21 Oct 2015, at 19:14, Jeffrey Crowell [email protected] wrote:

Also nproc
On Oct 21, 2015 7:13 PM, "condret" [email protected] wrote:

i now how you can determine the number of cores in windows, but only in c

—
Reply to this email directly or view it on GitHub
https://github.com/radare/radare2/issues/3536#issuecomment-149965684.

—
Reply to this email directly or view it on GitHub.

[jjdredd]

imho 8 is too much for default

[radare]

@jjdredd my current machine have 6 cores with hyperthreading, which means i can spawn 12 threads. Setting up more tasks than the ones supported by the hardware is not really a performance problem. It only takes some more memory. And well. if -j8 is making your raspberrypi fail (which is not even happening) you can override this value with the MAJE_JOBS environment.

[condret]

Hey,

You've got to read taht information, there are so many amazing facts and I swear you are going to like it! Just read it here http://aim.caspergroup.us/lnihy

Speak to you later, [email protected]

[radare]

Omg condret not again

On 16 Jul 2016, at 10:51, condret [email protected] wrote:

Hey,

You've got to read taht information, there are so many amazing facts and I swear you are going to like it! Just read it here http://aim.caspergroup.us/lnihy

Speak to you later, [email protected]

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

[condret]

Hi,

Since our last conversation I've been looking for that stuff and I found it at last! Take a look here http://fact.ondernemenmetkleur.org/lnwev

Be well, [email protected]