Menu
▾
▴
[G4l-general] More updates, addition of lzop compress, and settings for more speed
|
From: Michael D. S. I. <mi...@ku...> - 2005-02-14 16:03:59
|
<?xml version="1.0" ?><html> <head> <title></title> </head> <body> <div align="left"><font face="Arial"><span style="font-size:10pt">I've made some more modifications to the g4l in the latest version.</span></font></div> <div align="left"><font face="Arial"><span style="font-size:10pt">ftp://202.128.73.29/g4lkrn5.iso</span></font></div> <div align="left"><font face="Arial"><span style="font-size:10pt">I've made the bzImage4 kernel the default, which is with all options and P4, smp, and hyperthread support. It loads on my Athlon, but it does say it may be slower on a non-P4 or multi processor/hyperthread machine, so bzImage3 should be used in that case.</span></font></div> <div align="left"><br/> </div> <div align="left"><font face="Arial"><span style="font-size:10pt">I have been trying to find ways to make it run faster, and have added lzop compression as an options. At first, it would create an image in about half the time of gzip, but would take about the same time to restore. About 2 hours for both with Gzip, and 1 hour to create with lzop, and just under 2 hours for lzop. (80GB drive with 3 OS's). The gzip image was about 15% smaller at about 12.8GB to 14.75GB for the lzop. </span></font></div> <div align="left"><br/> </div> <div align="left"><font face="Arial"><span style="font-size:10pt">I tested some options with bs, and with a bs=1M, I was able to get the restore and backup both under 1 hour. </span></font></div> <div align="left"><br/> </div> <div align="left"><font face="Arial"><span style="font-size:10pt">The lzop compressor also uses less CPU than Gzip. Gzip would be as high as 90+%, while lzop would run about 30%. </span></font></div> <div align="left"><br/> </div> <div align="left"><font face="Arial"><span style="font-size:10pt">I've also tried hdparm options, but they don't seem to make a difference. With kernel bzImage4, the dma is turned on, but the -c option is set to 16 bits. If one wants to try the options, under the special commands, one could enter.</span></font></div> <div align="left"><font face="Arial"><span style="font-size:10pt">hdparm /dev/hda (or whatever dev)</span></font></div> <div align="left"><font face="Arial"><span style="font-size:10pt">to see the settings.</span></font></div> <div align="left"><font face="Arial"><span style="font-size:10pt">hdparm -c3 -d1 -u1 /dev/hda</span></font></div> <div align="left"><font face="Arial"><span style="font-size:10pt">would set the highest parameters, but might be dangerous with some systems. </span></font></div> <div align="left"><br/> </div> <div align="left"><font face="Arial"><span style="font-size:10pt">With the lastest jetcat-mod, I have it reporting the MB/sec, and was able to get 23.8MB/second on the create and 21.89MB/second on the restore with a 100Mb Ethernet. </span></font></div> <div align="left"><br/> </div> <div align="left"></div> </body> </html> |
