Mprime questions...

Xyzzy · 2003-03-24, 03:47

What compiler is used to compile mprime? Would the Intel compiler be a worthwhile investment?

What optimizations are used? If just the basic optimizations are used, does using some of the more "dangerous" ones make much of a difference in speed?

I know how to run mprime from a cron job... How can I do that *and* send everything you'd normally see with "mprime -d" to a file?

On a headless, dedicated box, should mprime be installed in /usr/local? What user should run it via cron?

Given that Linux has less stuff running can I expect work to be done faster on a non-X Linux box versus a Windows box?

Thanks!

QuintLeo · 2003-03-24, 04:35

On the same hardware, LINUX seems to run a hair faster - but it's not a big difference if you don't have a lot of "extra" stuff running on the Windoze box.

Especially under NT (I can't speak to XP or 2k).

I thought the major Prime code was written in assembler? If so, a compiler change won't have a noticeable effect if any at all.

I start up my mprime detached with a line like this

(cd /mersenne ; exec ./mprime -d > /dev/tty10 2>&1) &

You should be able to put that as a single commend inside a chrontab line, substituting a file name for the /dev/tty10

I see no reason for mprime to have to go into /usr/local - seems to be a personal preference thing. I don't mess around with having multiple users on a dedicated cracker box, so I have no idea what user to put if you don't use root as the user. I'd guess that it would have to be a user with execute and read privilages to the executable, and read and write to the directory the other config/intermediate files are stored in.

garo · 2003-03-24, 06:46

Quint is right. My crontab line reads something like this

1 0 * * * cd /path/to/mprime; ./mprime -d >> log.txt &

That works just beautifully. Yeah every day I get an extra line in my log.txt saying "another mprime running " but that's okay :)

QuintLeo · 2003-03-24, 16:19

While I'm thinkinsg about it - why run mprime from cron in the first place on a headless dedicated box?

I'd think it would be more efficient to just put it into rc.local for startup on bootup (or equivilent for non-Slackware distributions)?

Most of my dedicated crackers I don't even bother installing cron on any more - it doesn't eat a LOT of CPU cycles, but it does eat SOME....

Xyzzy · 2003-03-24, 18:11

Quote:

Originally Posted by QuintLeo

While I'm thinkinsg about it - why run mprime from cron in the first place on a headless dedicated box?

If mprime stops for whatever reason cron will restart it... You can't do that with a script in rc.local...

IMO, the interval for cron should be one hour or less... The cycles cron uses is negligible... Losing mprime output for a possible 23 hours and 59 minutes is a bigger problem...

NookieN · 2003-03-24, 18:24

I have mprime launched a boot-time by init, with this line in the inittab:

prim:2345:boot:/var/mprime/mprime -B

I'm not sure why you'd want cron restarting mprime if it keeps crashing. When mprime dies with no error (usually due to seg fault) I take it as an indication my results are becoming corrupt.

2003-03-24, 03:47	#1
Xyzzy "Mike" Aug 2002 2×23×179 Posts	Mprime questions... What compiler is used to compile mprime? Would the Intel compiler be a worthwhile investment? What optimizations are used? If just the basic optimizations are used, does using some of the more "dangerous" ones make much of a difference in speed? I know how to run mprime from a cron job... How can I do that and send everything you'd normally see with "mprime -d" to a file? On a headless, dedicated box, should mprime be installed in /usr/local? What user should run it via cron? Given that Linux has less stuff running can I expect work to be done faster on a non-X Linux box versus a Windows box? Thanks!

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
NFS questions	JohnFullspeed	Factoring	23	2011-07-21 17:03
some questions about 64bit mprime	rudi_m	Software	6	2006-04-14 23:32
Problem with mprime (Fixed with mprime -d)	antiroach	Software	2	2004-07-19 04:07
Linux and mprime pre-newbie questions	eepiccolo	Software	4	2003-02-11 09:20
A few questions :)	xtreme2k	Lounge	59	2002-10-31 06:20

2003-03-24, 04:35	#2
QuintLeo Oct 2002 Lost in the hills of Iowa 2⁶·7 Posts	On the same hardware, LINUX seems to run a hair faster - but it's not a big difference if you don't have a lot of "extra" stuff running on the Windoze box. Especially under NT (I can't speak to XP or 2k). I thought the major Prime code was written in assembler? If so, a compiler change won't have a noticeable effect if any at all. I start up my mprime detached with a line like this (cd /mersenne ; exec ./mprime -d > /dev/tty10 2>&1) & You should be able to put that as a single commend inside a chrontab line, substituting a file name for the /dev/tty10 I see no reason for mprime to have to go into /usr/local - seems to be a personal preference thing. I don't mess around with having multiple users on a dedicated cracker box, so I have no idea what user to put if you don't use root as the user. I'd guess that it would have to be a user with execute and read privilages to the executable, and read and write to the directory the other config/intermediate files are stored in.

2003-03-24, 06:46	#3
garo Aug 2002 Termonfeckin, IE 5314₈ Posts	Quint is right. My crontab line reads something like this 1 0 * * * cd /path/to/mprime; ./mprime -d >> log.txt & That works just beautifully. Yeah every day I get an extra line in my log.txt saying "another mprime running " but that's okay :)

2003-03-24, 16:19	#4
QuintLeo Oct 2002 Lost in the hills of Iowa 700₈ Posts	While I'm thinkinsg about it - why run mprime from cron in the first place on a headless dedicated box? I'd think it would be more efficient to just put it into rc.local for startup on bootup (or equivilent for non-Slackware distributions)? Most of my dedicated crackers I don't even bother installing cron on any more - it doesn't eat a LOT of CPU cycles, but it does eat SOME....

2003-03-24, 18:24	#6
NookieN Aug 2002 2·29 Posts	I have mprime launched a boot-time by init, with this line in the inittab: prim:2345:boot:/var/mprime/mprime -B I'm not sure why you'd want cron restarting mprime if it keeps crashing. When mprime dies with no error (usually due to seg fault) I take it as an indication my results are becoming corrupt.