Best boot code for tinycore 4.7.7

[malikawan]

i need to start my tiny core in 15 to 20 seconds with my java application. i am running only java application and my boot code that i use :-

linux /boot/vmlinuz quiet console=/dev/null libata.dma=0 tce=sda1 home=sda1 opt=sda1 noicons nodhcp
initrd /boot/core.gz

my tiny core is installed on 1 gb sd card
and i create a script to run my jar file in .X.d to auto start on boot.
problem is that when i boot it open my application about 33 to 35 seconds

Any suggestion Please

Malik Awan

[Rich]

Hi malikawan
I suggest you add the following boot codes:

Code: [Select]

printk.time=Y syslogThen open the  /var/log/messages  file. It will contain timing information allowing you to determine where the bottlenecks are.
I suspect you will find loading Java is slowing you down.

[malikawan]

Sir how can i determine where the bottlenecks are?
my printk.time=y syslog file is attached

[curaga]

Your log shows the boot only taking about 5 seconds up to the start of your Java app. And you have some ext4 corruption on your card.

So any slowness is either from your Java app, or from the bootloader loading the kernel slowly.

[malikawan]

Sir where you find that boot start in 5 sec. Do you calculate the time by adding all fig or its present in file that boot time 5 sec

Malik Awan

[curaga]

[    4.736509] The number inside brackets shows time since kernel start. At that point the WM was up.

One second later your Java app starts.

[malikawan]

When i manually start the java application after x it take 12 seconds so if my  boot start in 5 seconds its means 12+5 = 17 seconds so in 17 seconds my java application run after power on but its start 30 to 32 seconds now

[tinypoodle]

You omitted the time before kernel boot in your equation, e.g. BIOS POST, bootloader, decompression.

Are you really referring to CorePlus?
If so why, if time seems to be crucial to you?

[Rich]

Hi malikawan

When i manually start the java application after x it take 12 seconds ...

Was the script to auto start your application disabled when you made that measurement? If it started and you then shut down
the application and then manually restarted it, your timing is not valid since your application was cached.

[malikawan]

Thanx sir