From: Robert W. <ro...@us...> - 2001-09-21 21:17:47
|
The proc01 test will run much faster if the -b option is used: proc01 -v -b:1024 By default the test uses the maximum size, which is set to 65536 or 64Kb. This seems to cause the long test time. I used 1024 and got better results, but you may want to play around with this number to see what you get. You may also want to run with the -v option to get verbose output. - Robbie Robert V. Williamson Linux Test Project IBM Linux Technology Center Phone: (512) 838-9295 T/L: 638-9295 http://ltp.sourceforge.net "John Elion" <je...@ti...> To: "Paul Larson" <pl...@au...> Sent by: cc: <ltp...@li...> ltp...@li...urc Subject: RE: [LTP] Test Time eforge.net 09/21/2001 01:12 PM Thank you for your reply. The test I referred to ("took 72 hours") was a reference from these [LTP] message archives (July 2001) concerning "proc01". I had no problem with the scripts. I am fairly new to a Unix environment but had no problem reading the scripts and understanding what was happening and what the underlying structure was. John Elion -----Original Message----- From: ltp...@li... [mailto:ltp...@li...]On Behalf Of Paul Larson Sent: Friday, September 21, 2001 10:06 AM To: John Elion Cc: ltp...@li... Subject: Re: [LTP] Test Time On 21 Sep 2001 13:47:00 -0400, John Elion wrote: > First, thanks to the contributors. This is a great idea; I appreciate the > efforts of the contributors. > > After reviewing the results pages of LTP and seeing that there was a series > of tests that stretched the kernel for 96 hours, I downloaded LTP and ran > the make and "runalltests.sh" on RedHat 7.1. The entire series executed in > about 20 minutes. That sounds about right for one pass through the script. When we run it, we put -s0 to tell it to keep running these tests forever (or until we stop the script). That way we can get long runs out of it. > I did see something about 1 of the tests taking 72 hours, but it looked like > that was a bug. Was it, or was that particular test left out of > "runalltests" so that it would complete quickly? Which test was that? I'm guessing it was one of the memory stress tests. There are some tests like that, that are left out of the runalltests.sh script. We leave it to the person conducting the test to decide if they want to execute them and run them manually. I'd like to add something in the not-so-distant future that allows you to pick which tests you want run, define parameters to Pan (run in random order, 5 at a time, continuously, etc...). In my head, I'm imagining something sort of like what you get when you 'make menuconfig' on the linux kernel. The two biggests problems I see are 1) what to use, as to insure that it will work on the widest variety of systems without requiring other packages to be installed, and 2) it needs to have a contstantly updated list of what tests exist, what options they can take, and a description for what they are testing. If someone has some bright ideas on this and wants to work on it, I think that would be great. Otherwise, scripts will have to do for now. As it stands though it's very easy to add tests to what gets run. Take a look at the runtest directory and if you want to add another test to what's getting run by runalltests.sh, just add it to one of the files in there that it uses. Also, if you haven't already looked at it, you may want to check out what's in the CVS tree. It's very close to being released and adds a LOT of new testcases. Thanks, Paul Larson _______________________________________________ Ltp-list mailing list Ltp...@li... https://lists.sourceforge.net/lists/listinfo/ltp-list _______________________________________________ Ltp-list mailing list Ltp...@li... https://lists.sourceforge.net/lists/listinfo/ltp-list |