On Fri, Aug 14, 2015 at 11:09:17AM +0530, Sudip Mukherjee wrote: > On Wed, Aug 12, 2015 at 05:40:28PM +0300, Dan Carpenter wrote: > > On Wed, Aug 12, 2015 at 01:59:20PM +0530, Sudip Mukherjee wrote: > > > Just started with it from yesterday. Initial database building took > > > almost yesterday full day and night. Today while building it took > > > around 1.5 hours. > > > > You mean that it took 24 hours to build the DB and 1.5 to retest the > > kernel using the database? > Sorry, could not reply yesterday. > First time the DB was built it took more than 13 hours to complete. > Not exactly sure how much, i left the computer on to complete this while > going home from work. From home I checked once and saw that it was still > running. Then it was almost 13 hours after starting. Way longer than I would expect. > > > > Sorry for that... > no problem. we are here for this only, :) > And this is only for the first time. Next time I again ran > build_kernel_data.sh , it was something around 1.5 - 2 hours. Now > test_kernel.sh is running on another terminal, lets see how much time it > takes. > >What kind of a computer are you using? RAM and > > number of cores? Do you have hyperthreading? > 64bit, 4 core, 8GB ram, CPU MHz: 3000.000 hyperthreading not there. > Just one thing, your test_kernel.sh was taking NR_CPU as 4, I hardcoded > that to 8. Can that be the problem? I don't think it is a good idea, but I haven't tested. Things end up fighting over the CPU so it could be a slow down. Building the database has been highly optimized by trial and error for my personal system. Anyway, reset the NR_CPU and let me know if it's compiling or buiding the database which is the problem. regards, dan carpenter -- To unsubscribe from this list: send the line "unsubscribe smatch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
