Previous Thread
Next Thread
Print Thread
Page 3 of 3 1 2 3
Re: Compile stats [Re: Golden Child] #113170
04/20/18 05:31 PM
04/20/18 05:31 PM
Joined: Feb 2014
Posts: 150
G
Golden Child Offline OP
Senior Member
Golden Child  Offline OP
Senior Member
G
Joined: Feb 2014
Posts: 150
Oh, and how does it perform using the nbd swap and ext file?


Limiting the memory to 512M with mem=512M on the linux boot parameter: (15 hours 8 minutes 45% cpu)


Code
INSPIRON_6400_COMPILE_NEW_DEBIAN93_NBD_SWAP_AND_EXT2_J4_WITH_512M.txt

50648   Compiling generated/mame/mame/drivlist.cpp...
50657   Linking mame...
54470   20060.38user 4745.05system 15:07:49elapsed 45%CPU (0avgtext+0avgdata 437428maxresident)k
54470   797521912inputs+4718016outputs (41895787major+169318284minor)pagefaults 0swaps
54470   DONE - COMPILE COMPLETE
================================================================================
EXECUTING: cat /proc/meminfo | grep "MemTotal"
MemTotal:         509780 kB
================================================================================
EXECUTING: lscpu | grep "Model name:"
Model name:            Genuine Intel(R) CPU           T2500  @ 2.00GHz
================================================================================
EXECUTING: ls -l ./mame
-rwxr-xr-x 1 golden golden 226877704 Apr 18 12:54 ./mame
================================================================================
EXECUTING: md5sum ./mame
edf1bf33710bd1d52c9720e69e66de7c  ./mame
================================================================================
EXECUTING: gcc --version | head -n 1
gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516
================================================================================





Boosting the memory back to 3GB but still using the nbd ext2: (2 hours 48 minutes 185% cpu)


Code
INSPIRON_6400_COMPILE_NEW_DEBIAN93_NBD_EXT2_J4_WITH_3GB_MEM.txt
================================

9986    Linking mame...
10078   17721.81user 967.77system 2:47:57elapsed 185%CPU (0avgtext+0avgdata 2447428maxresident)k
10078   2513320inputs+4609576outputs (34354major+157379289minor)pagefaults 0swaps
10078   DONE - COMPILE COMPLETE
================================================================================
EXECUTING: cat /proc/meminfo | grep "MemTotal"
MemTotal:        3106596 kB
================================================================================
EXECUTING: lscpu | grep "Model name:"
Model name:            Genuine Intel(R) CPU           T2500  @ 2.00GHz
================================================================================
EXECUTING: ls -l ./mame
-rwxr-xr-x 1 golden golden 226877704 Apr 18 22:11 ./mame
================================================================================
EXECUTING: md5sum ./mame
edf1bf33710bd1d52c9720e69e66de7c  ./mame
================================================================================
EXECUTING: gcc --version | head -n 1
gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516
================================================================================

Re: Compile stats [Re: Golden Child] #113185
04/21/18 11:02 PM
04/21/18 11:02 PM
Joined: Feb 2014
Posts: 150
G
Golden Child Offline OP
Senior Member
Golden Child  Offline OP
Senior Member
G
Joined: Feb 2014
Posts: 150
So why does the compiled binary md5sum and the file size change when you change the comple directory path?

Running strings on the mame binary shows the compile path embedded within:

Code
$ strings /mnt/c/mame194_extract/mame/mame | grep "/mnt/c"
/mnt/c/mame194_extract/mame/build/projects/sdl/mame/gmake-linux


and I couldn't understand why a diff would show that the png.pyc was different also, for the exact same reason:

Code
$ strings /mnt/c/mame194_extract/mame/scripts/build/png.pyc | grep "/mnt/c"
/mnt/c/mame194_extract/mame/scripts/build/png.pyt
/mnt/c/mame194_extract/mame/scripts/build/png.pyt
/mnt/c/mame194_extract/mame/scripts/build/png.pyt
/mnt/c/mame194_extract/mame/scripts/build/png.pyR
/mnt/c/mame194_extract/mame/scripts/build/png.pyR
/mnt/c/mame194_extract/mame/scripts/build/png.pyt
...

Re: Compile stats [Re: Golden Child] #113191
04/23/18 12:58 AM
04/23/18 12:58 AM
Joined: Feb 2014
Posts: 150
G
Golden Child Offline OP
Senior Member
Golden Child  Offline OP
Senior Member
G
Joined: Feb 2014
Posts: 150
So here's a question you've always wanted to know the answer to:

Inside of the mame binary, how many times does the word mame appear?

(from the mame194 binary)

Code
$ strings mame64 | grep -i mame | wc -l 
37062

Re: Compile stats [Re: Golden Child] #113192
04/23/18 01:35 AM
04/23/18 01:35 AM
Joined: Mar 2001
Posts: 16,070
USA
R
R. Belmont Offline
Very Senior Member
R. Belmont  Offline
Very Senior Member
R
Joined: Mar 2001
Posts: 16,070
USA
That seems high. What happens if it's a stripped binary with no debug symbols/symbol paths?

Re: Compile stats [Re: R. Belmont] #113193
04/23/18 02:42 AM
04/23/18 02:42 AM
Joined: Feb 2014
Posts: 150
G
Golden Child Offline OP
Senior Member
Golden Child  Offline OP
Senior Member
G
Joined: Feb 2014
Posts: 150
Yes, it's mostly probably symbol paths.

Code
$ strings mame64 | grep -i "src/mame" | wc -l
35717


So at least 35717 are symbol paths.

It's interesting to see all of the mame strings that aren't "src/mame" paths

Most of them are mangled function names.

Code
$ strings mame64 | grep -i "mame" |  grep -i -v "src/mame" | less

D$`mameH
MAME
MAMESAVEI
MAMESAVEUSH
MAMESAVEL
MAMESAVEH9D$ 
MAMESAVEH9D$ 
MAME
and the MAME team
http://mamedev.org
Copyright Nicola Salmoria and the MAME team
18object_finder_baseI19netlist_mame_deviceLb1EE
...

Re: Compile stats [Re: Golden Child] #113402
05/12/18 04:00 AM
05/12/18 04:00 AM
Joined: Feb 2014
Posts: 150
G
Golden Child Offline OP
Senior Member
Golden Child  Offline OP
Senior Member
G
Joined: Feb 2014
Posts: 150
For more silly fun I thought I'd try to compile mame with Debian 9.3 on just about every x86 pc that I own.


There was this old Pentium 3 933mhz that wanted to compile mame so badly but it only had 512mb ram.



So I did the NBD network block device thing and used another 16GB system on the network and gave it access to a 4GB ext2 file system and a 4GB swap file.

I forgot how I did it before, so I printed up my previous post and noticed I left out a couple of things:

I forgot to "sudo modprobe nbd" before I did the nbd-client command lines.

So:

Code
sudo modprobe nbd
sudo nbd-client  192.168.0.10 10809 /dev/nbd0 -N nbdfileswap -s
sudo nbd-client  192.168.0.10 10809 /dev/nbd1 -N nbdfileext2



Also I needed to chown the nbd-server export files or I'd get problems when I'd try to format them with mkswap

On the server system:

Code
sudo chown me:me /mnt/a/NBDFILESWAP
sudo chown me:me /mnt/a/NBDFILEEXT2


On the client system:

Code
sudo mkswap /dev/nbd0
sudo swapon /dev/nbd0 -p 1024

sudo mke2fs /dev/nbd1 -t ext4



And if I wanted to make my compiles have the same md5sum, they would have to have the same source directory name.

My compile directory name is : Downloads/mame194_extract/mame

So I took the mame194_extract directory and renamed it old_mame194_extract with

Code
cd Downloads
mv mame194_extract old_mame194_extract
mkdir mame194_extract


Now we can mount the /dev/nbd1 filesystem in the mame194_extract directory.

Code
sudo mount /dev/nbd1 mame194_extract -t ext4


and now we can copy the mame directory into the mounted spot.


I always seem to have problems with permissions so let's mkdir the mame directory and do some permissions fiddling.
(me represents my username)

when you do the sudo mount it will set the permissions of the mame194_extract directory to root, so lets see if we can take ownership back.

Code
sudo chown me:me mame194_extract
cd mame194_extract

sudo mkdir mame
sudo chown me:me mame
cp -r ../old_mame194_extract/mame mame


and to do the compile line:
Code
make clean; /usr/bin/time make -j1 2>&1 | lua5.3 lua_time.lua | tee MY_COMPILE_LOG.txt | nl



Everything ran great until the link phase where it crashed!!!! There was a strange kernel panic.

Code
90698   Building driver list...
90703   22746 driver(s) found
90703   Compiling generated/mame/mame/drivlist.cpp...
90737   Compiling generated/version.cpp...
90737   Linking mame...

*BOOM*


So after a reboot, I reconnected to the swap:
Code
sudo modprobe nbd
sudo nbd-client  192.168.0.10 10809 /dev/nbd0 -N nbdfileswap -s
sudo nbd-client  192.168.0.10 10809 /dev/nbd1 -N nbdfileext2

sudo swapon /dev/nbd0 -p 1024

cd Downloads
cd mame194_extract
cd mame

/usr/bin/time make -j1 2>&1 | tee MY_COMPILE_LOG_RESUME.txt | nl


and the compile looked good, matching my normal md5sum.
Code
0       GCC 6.3.0 detected
14      Linking mame...
2290    170.60user 297.71system 38:09.45elapsed 20%CPU (0avgtext+0avgdata 466176maxresident)k
2290    41853528inputs+604888outputs (3173985major+2168783minor)pagefaults 0swaps
2290    DONE - COMPILE COMPLETE
================================================================================
EXECUTING: cat /proc/meminfo | grep "MemTotal"
MemTotal:         508552 kB
================================================================================
EXECUTING: lscpu | grep "Model name:"
Model name:            Pentium III (Coppermine)
================================================================================
EXECUTING: lscpu
Architecture:          i686
CPU op-mode(s):        32-bit
Byte Order:            Little Endian
CPU(s):                1
On-line CPU(s) list:   0
Thread(s) per core:    1
Core(s) per socket:    1
Socket(s):             1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 8
Model name:            Pentium III (Coppermine)
Stepping:              6
CPU MHz:               931.023
BogoMIPS:              1862.04
Flags:                 fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pse36 mmx fxsr sse eagerfpu
================================================================================
EXECUTING: md5sum ./mame
3ad480dbe397219dc37c40b82a97029d  ./mame


If we add 2290 to 90737 we get 93027 seconds = 1550 minutes = 25.84 hours

what kind of chip you got in there a Dorito?

Re: Compile stats [Re: Golden Child] #113462
05/23/18 01:08 AM
05/23/18 01:08 AM
Joined: Feb 2014
Posts: 150
G
Golden Child Offline OP
Senior Member
Golden Child  Offline OP
Senior Member
G
Joined: Feb 2014
Posts: 150
And for my latest pointless compile, I wanted to see if an old Pentium II 400mhz could compile mame. It's only got 512mb ram so we'll use NBD to help out. The Dell Inspiron 7500 laptop wouldn't boot from USB since the bios doesn't support it so I installed Debian 9.4 from cd directly to the internal 10GB hard drive. It didn't have ethernet but it did have PCMCIA so I chucked a USB 2.0 PCMCIA card and used a USB ethernet card so I could get debian packages from the internet.

I had problems getting X working so I just switched to a text terminal and worked from there.



It's an order of magnitude slower and it takes 60 hours to compile. A watched pot never boils!

Code
198378	Linking mame...
217521	153726.70user 10739.85system 60:25:20elapsed 16%CPU (0avgtext+0avgdata 474592maxresident)k
217521	283493600inputs+4532320outputs (8194091major+157393150minor)pagefaults 0swaps
217521	DONE - COMPILE COMPLETE
================================================================================
EXECUTING: cat /proc/meminfo | grep "MemTotal"
MemTotal:         509256 kB
================================================================================
EXECUTING: lscpu | grep "Model name:"
Model name:            Mobile Pentium II
================================================================================
EXECUTING: lscpu
Architecture:          i686
CPU op-mode(s):        32-bit
Byte Order:            Little Endian
CPU(s):                1
On-line CPU(s) list:   0
Thread(s) per core:    1
Core(s) per socket:    1
Socket(s):             1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 6
Model name:            Mobile Pentium II
Stepping:              10
CPU MHz:               400.026
BogoMIPS:              800.05
Flags:                 fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pse36 mmx fxsr eagerfpu
================================================================================
EXECUTING: lspci -nn | grep -E -i "Display|VGA"
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Rage Mobility AGP 2x Series [1002:4c4d] (rev 64)
================================================================================
EXECUTING: ls -l ./mame
-rwxr-xr-x 1 golden golden 226877720 May 21 18:53 ./mame
================================================================================
EXECUTING: md5sum ./mame
7693392c7f258978b95da32a876370f0  ./mame
================================================================================
EXECUTING: gcc --version | head -n 1
gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516
================================================================================



but wait! the md5sum doesn't match the compile on my other system!

The file size is the same but the md5sum is different.

This time I decided to use git to clone the mame repository with "git clone https://github.com/mamedev/mame.git" and "git checkout mame0194".

Then I commented out the barcrest and bfm machines since I had problems compiling them on 32 bit.

So why does it differ?

It has to do with build/generated/git_desc.

In the makefile it makes git_desc, calling "git describe --dirty" and that description gets compiled into your binary.

Code
grep "git describe" makefile
NEW_GIT_VERSION := $(shell git describe --dirty)



If you uncomment the line IGNORE_GIT=1 then it will set git_desc to (unknown).


All of my other compiles had come from extracting the mame0194 zip without using git. If you do it that way, you get an (unknown) git_desc I believe.

So uncommenting IGNORE_GIT=1 in the makefile and running make again takes 6 hours 15 minutes and it reads the identical md5sum.

Code
922	Compiling generated/version.cpp...
926	Linking mame...
22549	991.58user 906.03system 6:15:49elapsed 8%CPU (0avgtext+0avgdata 468072maxresident)k
22549	42756488inputs+694864outputs (2955975major+2339412minor)pagefaults 0swaps
22549	DONE - COMPILE COMPLETE
================================================================================
EXECUTING: cat /proc/meminfo | grep "MemTotal"
MemTotal:         509256 kB
================================================================================
EXECUTING: lscpu | grep "Model name:"
Model name:            Mobile Pentium II
================================================================================
EXECUTING: lscpu
Architecture:          i686
CPU op-mode(s):        32-bit
Byte Order:            Little Endian
CPU(s):                1
On-line CPU(s) list:   0
Thread(s) per core:    1
Core(s) per socket:    1
Socket(s):             1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 6
Model name:            Mobile Pentium II
Stepping:              10
CPU MHz:               400.026
BogoMIPS:              800.05
Flags:                 fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pse36 mmx fxsr eagerfpu
================================================================================
EXECUTING: lspci -nn | grep -E -i "Display|VGA"
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Rage Mobility AGP 2x Series [1002:4c4d] (rev 64)
================================================================================
EXECUTING: ls -l ./mame
-rwxr-xr-x 1 golden golden 226877720 May 22 11:45 ./mame
================================================================================
EXECUTING: md5sum ./mame
3ad480dbe397219dc37c40b82a97029d  ./mame
================================================================================
EXECUTING: gcc --version | head -n 1
gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516
================================================================================
EXECUTING: lsb_release -a
Distributor ID:	Debian
Description:	Debian GNU/Linux 9.4 (stretch)
Release:	9.4
Codename:	stretch
================================================================================
EXECUTING: uname -a
Linux debian94golden 4.9.0-6-686-pae #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) i686 GNU/Linux
================================================================================



You're using a pentium 2 400 don't make me laugh!

Your mame compiles in 2 days and a half!

Re: Compile stats [Re: Golden Child] #113475
05/26/18 01:03 AM
05/26/18 01:03 AM
Joined: Feb 2014
Posts: 150
G
Golden Child Offline OP
Senior Member
Golden Child  Offline OP
Senior Member
G
Joined: Feb 2014
Posts: 150
Here's a list with all of the different cpus and memory sizes that I've compiled mame194 with on debian 9.3 32 bit.



Code
COREI7_2600_AT_3.40GHZ_J4.txt:2039	7329.76user 281.14system 33:58.50elapsed 373%CPU (0avgtext+0avgdata 2556336maxresident)k
COREI7_2600_AT_3.40GHZ_J4.txt:MemTotal:        3357688 kB
COREI7_2600_AT_3.40GHZ_J4.txt-================================================================================
COREI7_2600_AT_3.40GHZ_J4.txt:EXECUTING: lscpu | grep "Model name:"
COREI7_2600_AT_3.40GHZ_J4.txt:Model name:            Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
COREI7_2600_AT_3.40GHZ_J4.txt-================================================================================


CORE_I5_2500_AT_2.70GHZ_8GBRAM_J4.txt:2479	8944.51user 340.61system 41:18.66elapsed 374%CPU (0avgtext+0avgdata 
CORE_I5_2500_AT_2.70GHZ_8GBRAM_J4.txt:MemTotal:        3278144 kB
CORE_I5_2500_AT_2.70GHZ_8GBRAM_J4.txt:================================================================================
CORE_I5_2500_AT_2.70GHZ_8GBRAM_J4.txt:EXECUTING: lscpu | grep "Model name:"
CORE_I5_2500_AT_2.70GHZ_8GBRAM_J4.txt:Model name:            Intel(R) Core(TM) i5-2500S CPU @ 2.70GHz
CORE_I5_2500_AT_2.70GHZ_8GBRAM_J4.txt:================================================================================

COREI3_2120_AT_3.3GHZ_J4.txt:3835	13185.30user 441.31system 1:03:55elapsed 355%CPU (0avgtext+0avgdata 2219012maxresident)k
COREI3_2120_AT_3.3GHZ_J4.txt:MemTotal:        3356012 kB
COREI3_2120_AT_3.3GHZ_J4.txt-================================================================================
COREI3_2120_AT_3.3GHZ_J4.txt:EXECUTING: lscpu | grep "Model name:"
COREI3_2120_AT_3.3GHZ_J4.txt:Model name:            Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz
COREI3_2120_AT_3.3GHZ_J4.txt-================================================================================

CORE2_E8400_3GHZ_J2.txt:5243	9545.29user 507.76system 1:27:23elapsed 191%CPU (0avgtext+0avgdata 2556616maxresident)k
CORE2_E8400_3GHZ_J2.txt:MemTotal:        3366192 kB
CORE2_E8400_3GHZ_J2.txt-================================================================================
CORE2_E8400_3GHZ_J2.txt:EXECUTING: lscpu | grep "Model name:"
CORE2_E8400_3GHZ_J2.txt:Model name:            Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz
CORE2_E8400_3GHZ_J2.txt-================================================================================


CORE2_2.13GHZ_J2_3GB.txt:14833.21user 782.10system 2:18:23elapsed 188%CPU (0avgtext+0avgdata 2556296maxresident)k
CORE2_2.13GHZ_J2_3GB.txt:MemTotal:        3097188 kB
CORE2_2.13GHZ_J2_3GB.txt-================================================================================
CORE2_2.13GHZ_J2_3GB.txt:EXECUTING: lscpu | grep "Model name:"
CORE2_2.13GHZ_J2_3GB.txt:Model name:            Intel(R) Core(TM)2 CPU          6400  @ 2.13GHz
CORE2_2.13GHZ_J2_3GB.txt-================================================================================

ATHLON_X2_4200_J2.txt:9082	16754.18user 835.16system 2:31:23elapsed 193%CPU (0avgtext+0avgdata 2556780maxresident)k
ATHLON_X2_4200_J2.txt:MemTotal:        3108024 kB
ATHLON_X2_4200_J2.txt-================================================================================
ATHLON_X2_4200_J2.txt:EXECUTING: lscpu | grep "Model name:"
ATHLON_X2_4200_J2.txt:Model name:            AMD Athlon(tm) 64 X2 Dual Core Processor 4200+
ATHLON_X2_4200_J2.txt-================================================================================

CORE_2GHZ_J2_3GB.txt:9398	17299.31user 894.90system 2:36:37elapsed 193%CPU (0avgtext+0avgdata 2556696maxresident)k
CORE_2GHZ_J2_3GB.txt:EXECUTING: cat /proc/meminfo | grep "MemTotal"
CORE_2GHZ_J2_3GB.txt:MemTotal:        3106644 kB
CORE_2GHZ_J2_3GB.txt-================================================================================
CORE_2GHZ_J2_3GB.txt:EXECUTING: lscpu | grep "Model name:"
CORE_2GHZ_J2_3GB.txt:Model name:            Genuine Intel(R) CPU           T2500  @ 2.00GHz
CORE_2GHZ_J2_3GB.txt-================================================================================


CORE_1.2GHZ_J2.txt:15626	27304.35user 1339.82system 4:20:25elapsed 183%CPU (0avgtext+0avgdata 1874264maxresident)k
CORE_1.2GHZ_J2.txt:MemTotal:        2059984 kB
CORE_1.2GHZ_J2.txt-================================================================================
CORE_1.2GHZ_J2.txt:EXECUTING: lscpu | grep "Model name:"
CORE_1.2GHZ_J2.txt:Model name:            Genuine Intel(R) CPU           U2500  @ 1.20GHz
CORE_1.2GHZ_J2.txt-================================================================================


XEON_2.4_2GB_J2.txt:18614	32568.25user 2098.30system 5:10:14elapsed 186%CPU (0avgtext+0avgdata 1849876maxresident)k
XEON_2.4_2GB_J2.txt:MemTotal:        2068336 kB
XEON_2.4_2GB_J2.txt-================================================================================
XEON_2.4_2GB_J2.txt:EXECUTING: lscpu | grep "Model name:"
XEON_2.4_2GB_J2.txt:Model name:            Intel(R) Xeon(TM) CPU 2.40GHz
XEON_2.4_2GB_J2.txt-================================================================================


VIA_VE900_J2_2GB.txt:18727	29077.54user 1737.50system 5:12:06elapsed 164%CPU (0avgtext+0avgdata 1639420maxresident)k
VIA_VE900_J2_2GB.txt:MemTotal:        1808424 kB
VIA_VE900_J2_2GB.txt-================================================================================
VIA_VE900_J2_2GB.txt:EXECUTING: lscpu | grep "Model name:"
VIA_VE900_J2_2GB.txt:Model name:            VIA Nano X2 L4050 @ 1.4 GHz
VIA_VE900_J2_2GB.txt-================================================================================


AMD_3500_J1_2GB_NEW_MEMORY.txt:19156	17261.50user 924.68system 5:19:15elapsed 94%CPU (0avgtext+0avgdata 1852420maxresident)k
AMD_3500_J1_2GB_NEW_MEMORY.txt:MemTotal:        2034832 kB
AMD_3500_J1_2GB_NEW_MEMORY.txt-================================================================================
AMD_3500_J1_2GB_NEW_MEMORY.txt:EXECUTING: lscpu | grep "Model name:"
AMD_3500_J1_2GB_NEW_MEMORY.txt:Model name:            AMD Athlon(tm) 64 Processor 3500+
AMD_3500_J1_2GB_NEW_MEMORY.txt-================================================================================


P4_2.4_2GB.txt:30882	28150.62user 1475.41system 8:34:41elapsed 95%CPU (0avgtext+0avgdata 1896448maxresident)k
P4_2.4_2GB.txt:MemTotal:        2066756 kB
P4_2.4_2GB.txt-================================================================================
P4_2.4_2GB.txt:EXECUTING: lscpu | grep "Model name:"
P4_2.4_2GB.txt:Model name:            Intel(R) Pentium(R) 4 CPU 2.40GHz
P4_2.4_2GB.txt-================================================================================

AMD_3500_J1_nbdswap_4G.txt:37641	19389.47user 1339.42system 10:27:20elapsed 55%CPU (0avgtext+0avgdata 448188maxresident)k
AMD_3500_J1_nbdswap_4G.txt:MemTotal:         508556 kB
AMD_3500_J1_nbdswap_4G.txt-================================================================================
AMD_3500_J1_nbdswap_4G.txt:EXECUTING: lscpu | grep "Model name:"
AMD_3500_J1_nbdswap_4G.txt:Model name:            AMD Athlon(tm) 64 Processor 3500+
AMD_3500_J1_nbdswap_4G.txt-================================================================================


EEEPC900A_ATOMN270_1.60ghz_J2_1GB_NBDSWAP.txt:44116	75574.29user 3516.67system 12:15:15elapsed 81%CPU (0avgtext+0avgdata 928748maxresident)k
EEEPC900A_ATOMN270_1.60ghz_J2_1GB_NBDSWAP.txt:MemTotal:        1020044 kB
EEEPC900A_ATOMN270_1.60ghz_J2_1GB_NBDSWAP.txt-================================================================================
EEEPC900A_ATOMN270_1.60ghz_J2_1GB_NBDSWAP.txt:EXECUTING: lscpu | grep "Model name:"
EEEPC900A_ATOMN270_1.60ghz_J2_1GB_NBDSWAP.txt:Model name:            Intel(R) Atom(TM) CPU N270   @ 1.60GHz
EEEPC900A_ATOMN270_1.60ghz_J2_1GB_NBDSWAP.txt-================================================================================



ATHLON1000_J1_2GB.txt:57018	52550.30user 2530.17system 15:50:18elapsed 21%CPU (0avgtext+0avgdata 1904392maxresident)k
ATHLON1000_J1_2GB.txt:MemTotal:        2068692 kB
ATHLON1000_J1_2GB.txt-================================================================================
ATHLON1000_J1_2GB.txt:EXECUTING: lscpu 
ATHLON1000_J1_2GB.txt:Model name:            AMD Athlon(tm) processor
ATHLON1000_J1_2GB.txt-CPU MHz:               1000.000
ATHLON1000_J1_2GB.txt-================================================================================


EEEPC701_CELERON_M_900MHZ_J1_512M_NBDSWAP.txt:89591	64814.87user 3980.20system 24:53:11elapsed 28%CPU (0avgtext+0avgdata 431512maxresident)k
EEEPC701_CELERON_M_900MHZ_J1_512M_NBDSWAP.txt:MemTotal:         501528 kB
EEEPC701_CELERON_M_900MHZ_J1_512M_NBDSWAP.txt-================================================================================
EEEPC701_CELERON_M_900MHZ_J1_512M_NBDSWAP.txt:EXECUTING: lscpu | grep "Model name:"
EEEPC701_CELERON_M_900MHZ_J1_512M_NBDSWAP.txt:Model name:            Intel(R) Celeron(R) M processor          900MHz
EEEPC701_CELERON_M_900MHZ_J1_512M_NBDSWAP.txt-================================================================================





P3_933_J1_512K_NBD.txt:90737	Linking mame... (crashed during the link, so had to reboot and resume)
P3_933_J1_512K_NBD_resume.txt:14	Linking mame...
P3_933_J1_512K_NBD_resume.txt:2290	170.60user 297.71system 38:09.45elapsed 20%CPU (0avgtext+0avgdata 466176maxresident)k

90737 + 2290 = 93027 seconds = 25.84 hours

P3_933_J1_512K_NBD_resume.txt:EXECUTING: cat /proc/meminfo | grep "MemTotal"
P3_933_J1_512K_NBD_resume.txt:MemTotal:         508552 kB
P3_933_J1_512K_NBD_resume.txt-================================================================================
P3_933_J1_512K_NBD_resume.txt-EXECUTING: lscpu
P3_933_J1_512K_NBD_resume.txt:Model name:            Pentium III (Coppermine)
P3_933_J1_512K_NBD_resume.txt-CPU MHz:               931.023
P3_933_J1_512K_NBD_resume.txt-================================================================================



P2_400_NBD_COMPILE.txt:217521	153726.70user 10739.85system 60:25:20elapsed 16%CPU (0avgtext+0avgdata 474592maxresident)k
P2_400_NBD_COMPILE.txt:MemTotal:         509256 kB
P2_400_NBD_COMPILE.txt-================================================================================
P2_400_NBD_COMPILE.txt:EXECUTING: lscpu | grep "Model name:"
P2_400_NBD_COMPILE.txt:Model name:            Mobile Pentium II
P2_400_NBD_COMPILE.txt-================================================================================
P2_400_NBD_COMPILE.txt-EXECUTING: lscpu
P2_400_NBD_COMPILE.txt:Model name:            Mobile Pentium II
P2_400_NBD_COMPILE.txt-CPU MHz:               400.026



Page 3 of 3 1 2 3

Moderated by  R. Belmont 

Who's Online Now
3 registered members (Reznor007, 2 invisible), 124 guests, and 2 spiders.
Key: Admin, Global Mod, Mod
Shout Box
Forum Statistics
Forums9
Topics8,606
Posts112,517
Members4,828
Most Online296
Dec 5th, 2018
Powered by UBB.threads™ PHP Forum Software 7.6.1.1
(Release build 20180111)
Page Time: 0.040s Queries: 14 (0.020s) Memory: 5.7255 MB (Peak: 5.9281 MB) Zlib enabled. Server Time: 2018-12-16 15:55:29 UTC