Hi, I've put up a page about preloading on openSUSE at [1]. This can drastically improve the startup time for some of the bigger applications. For example, my OpenOffice used to take 17 seconds. With preloading it only takes 6 seconds. I would like to hear if/how it works on your systems, so go ahead and try it out! There is also a TODO list, so you can contribute if you want to. Cheers nordi [1] http://www.opensuse.org/index.php/SUPER_preloading
Hi, You mention that it only works for KDE, but the only connection to KDE I can see is the autostart script. Should this procedure of preloading for OO and Firefox/Mozilla not work for all WM's with respective autostart scripts? Kashif On Tue, 2005-08-23 at 16:44 +0200, nordi wrote:
Hi,
I've put up a page about preloading on openSUSE at [1]. This can drastically improve the startup time for some of the bigger applications. For example, my OpenOffice used to take 17 seconds. With preloading it only takes 6 seconds.
I would like to hear if/how it works on your systems, so go ahead and try it out! There is also a TODO list, so you can contribute if you want to.
Cheers nordi
[1] http://www.opensuse.org/index.php/SUPER_preloading
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Kashif Sheikh wrote:
Should this procedure of preloading for OO and Firefox/Mozilla not work for all WM's with respective autostart scripts?
It certainly would. But I don't know enough about all the other WMs to know where exactly the autostart stuff needs to go. This is because KDE is the only WM that I use. But this issue is on my TODO list. Any help with this is welcome! nordi
On Wed, Aug 24, 2005 at 3:18 am, in message <430B3E34.9090106@addcom.de>, nordi@addcom.de wrote: Kashif Sheikh wrote: Should this procedure of preloading for OO and Firefox/Mozilla not work for all WM's with respective autostart scripts?
It certainly would. But I don't know enough about all the other WMs to know where exactly the autostart stuff needs to go. This is because KDE is the only WM that I use.
But this issue is on my TODO list. Any help with this is welcome!
Solved on http://www.opensuse.org/index.php/10.0_beta2_i686_SUPER All you need is to know what files are opened by the application during startup. You can use a script I found on another site and with strace and a little sed one can pretty much preload any application. Andreas
--- Andreas Girardet
On Wed, Aug 24, 2005 at 3:18 am, in message <430B3E34.9090106@addcom.de>, nordi@addcom.de wrote: Kashif Sheikh wrote: Should this procedure of preloading for OO and Firefox/Mozilla not work for all WM's with respective autostart scripts?
It certainly would. But I don't know enough about all the other WMs to know where exactly the autostart stuff needs to go. This is because KDE is the only WM that I use.
But this issue is on my TODO list. Any help with this is welcome!
Solved on
http://www.opensuse.org/index.php/10.0_beta2_i686_SUPER
All you need is to know what files are opened by the application during startup. You can use a script I found on another site and with strace and a little sed one can pretty much preload any application.
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Reg preloading any application ... I hope this will become an easy to use feature in SuSE/openSuSE/SUPER ... its something which has always been missing on Linux :-) ___________________________________________________________ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com
Reg preloading any application ... I hope this will become an easy to use feature in SuSE/openSuSE/SUPER ... its something which has always been missing on Linux :- )
The hooks are in openSUSE already. Nordi is going to put into bugzilla to do more aggressive preloading. In meantime I have found that Nordi's modifications slow the overall boottime down by 6 seconds and do not really provide much benefit with firefox ..... Can more people please try the following methods and give Nordi and me feedback on which one is faster/better: Nordi: http://www.opensuse.org/index.php/SUPER_preloading Andreas: http://www.opensuse.org/index.php/10.0_beta2_i686_SUPER#SUPER_preloading my benchmark times on the reference system comparing Nordi's and my method. I just find this very puzzling as I would not have thought there to be such a difference. http://www.opensuse.org/index.php/SUPER_standard_benchmark Ideally in preloading we would need some kind of daemon that creates preload files dynamically depending on what applications the user uses. Those files then have to be put on disc in a manner not to be too far apart and close together with the files used at boot. Ideally preload files and boot files need to be together on the first part of the disc. Such a daemon is certainly way beyond my capabilities, but if there is anyone on here who can program such a daemon, we can put this as an experimental feature into SUPER. Andreas
Andreas Girardet wrote:
In meantime I have found that Nordi's modifications slow the overall boottime down by 6 seconds and do not really provide much benefit with firefox .....
I think I might have an explanation for this: - Your preload will load English locale files while mine preloads German locale files (search for /usr/share/locale/). So my (German) preload files will not preload your (English) locale files. - Your preload is loading user-specific stuff! You ran the strace as user "root", so your preload also loads files from /root/.firefox. You have to exclude _all_ user-specific files from your preloading if you want to get real-world results. My parser removes any user-specific stuff from the list of preloaded files. The same is of course true for the locale. But when it comes to locale data the solution is easy: Preload English _and_ German files. On an English system there won't be any German locale files, so this will not slow you down measurably (and vice versa). Same thing for any other language! Please re-run the benchmark with those modifications and tell me if the difference is still that big. Cheers nordi
On Wed, Aug 24, 2005 at 9:13 pm, in message <430C3A1F.4030504@addcom.de>, nordi@addcom.de wrote: Andreas Girardet wrote: In meantime I have found that Nordi's modifications slow the overall boottime down by 6 seconds and do not really provide much benefit with firefox .....
I think I might have an explanation for this:
- Your preload will load English locale files while mine preloads German locale files (search for /usr/share/locale/). So my (German) preload files will not preload your (English) locale files.
- Your preload is loading user- specific stuff! You ran the strace as user "root", so your preload also loads files from /root/.firefox. You have to exclude _all_ user- specific files from your preloading if you want to get real- world results. My parser removes any user- specific stuff from the list of preloaded files.
The same is of course true for the locale. But when it comes to locale data the solution is easy: Preload English _and_ German files. On an English system there won't be any German locale files, so this will not slow you down measurably (and vice versa). Same thing for any other language!
Please re- run the benchmark with those modifications and tell me if the difference is still that big.
That makes sense .. can you however try my modifications on your system with german locales and let me know the difference. I really need you to crosscheck mine. Andreas
andreas, I have a question about this preloading: on my linux-PC will also run aVMware-GSX-system. I have tested it now for the last 1 1/2 days (with and without SUPER, with and without preloading, with the CK-kernel-patch and without it - so, many installs and many setups of all this systems and combinations .... smile). but it looks, that SUPER and SUPER + preloading will speed down the GSX-server, so that the VMs in there wouldn't run in the same propper way then without SUPER and / + preloading. I think the problem could be the amount of memory, and "where" (?) all the stuff will be put into it. so, what is what I have, and what I need: the PC has about 2 GB RAM, and the VMware-server needs about 1.2 GB RAM, for 2 Windows-boxes ( 512 MB for eatch, but they wouldn't run at the same time), and the rest for a SUSE9.3-box. the question is: is there any way to "tell" the system, how mutch of the RAM it can use, and maybe "where" or "what" peace of RAM it can use, so wthat other programs like VMware have no "trouble" ? thnaks, JBscout
the question is: is there any way to "tell" the system, how mutch of the RAM it can use, and maybe "where" or "what" peace of RAM it can use, so wthat other programs
like
VMware have no "trouble" ?
JBscout More of a VMWARE issue really .... start here: http://www.vmware.com/support/kb/enduser/std_adp.php?p_faqid=844 Regards, Andreas openSUSE is SUPER: To help in the SUSE Performance Enhanced Release project visit http://www.opensuse.org/index.php/SUPER
Andreas Girardet schrieb:
the question is: is there any way to "tell" the system, how mutch of the RAM it can
use,
and maybe "where" or "what" peace of RAM it can use, so wthat other programs
like
VMware have no "trouble" ?
JBscout
More of a VMWARE issue really .... start here:
http://www.vmware.com/support/kb/enduser/std_adp.php?p_faqid=844
Regards,
Andreas
Andreas, thanks for the link !! I will test that in the next days, esp. when I have downloaded the new beta-version. all this install, re-install, setup und re-setup needs to mutch time. not so lucky that the day has only 24 hours. smile. and "playing around" is not my work I have at the "normal" times of the day. but its the funny part of it ;)) JBScout
On Thu, Aug 25, 2005 at 1:32 pm, in message <430D1FC5.7090200@libitum.de>, jbscout_opsubeta@libitum.de wrote: Andreas Girardet schrieb:
the question is: is there any way to "tell" the system, how mutch of the RAM it can
use,
and maybe "where" or "what" peace of RAM it can use, so wthat other programs
like
VMware have no "trouble" ?
JBscout
More of a VMWARE issue really .... start here:
http://www.vmware.com/support/kb/enduser/std_adp.php?p_faqid=844
Regards,
Andreas
Andreas,
thanks for the link !! I will test that in the next days, esp. when I have downloaded the new beta- version.
all this install, re- install, setup und re- setup needs to mutch time. not so lucky that the day has only 24 hours. smile. and "playing around" is not my work I have at the "normal" times of the day. but its the funny part of it ;))
I know what you mean RE 24 hours. Luckily I am able to dedicate a lot of time to openSUSE at the moment. Might change though .... Install yourself a yast server (network install server) installed first and then install from that one, if you don't do this already, since it cuts down the actual install time quite a bit and you can just have it run unattended. With an autoyast.xml file you will even be able to install it completely unattended. This is what I do and it saves a lot of time. Andreas
Andreas Girardet schrieb:
I know what you mean RE 24 hours.
Luckily I am able to dedicate a lot of time to openSUSE at the moment. Might change though ....
yea, thats a lucky situation ;) ... my lucky situation is that beside I have to be one of the chiefs here, one of the programmer, one of the coordinator for our freelancer: I'm the one who has to deside with systems will beused in the future. ( and what makes me realy lucky. how many windows-systems there will be ... smile. not to mutch I think ).
Install yourself a yast server (network install server) installed first and then install from that one, if you don't do this already, since it cuts down the actual install time quite a bit and you can just have it run unattended. With an autoyast.xml file you will even be able to install it completely unattended. This is what I do and it saves a lot of time.
Andreas
yea, I've read that before in the thread. but never done it before. and the stuff around "autoyast.xml" I didn't understand exactly. has that to do with the tool "automatic install" ( or "Automatische Installation" in german; don't know the exact name in the english version) in YAST ? is there something in the documentation where u can point me to (I've got the boxed pro-version with the books of 9.3 if its in there .... ). thanks again, JBscout
I changed the subject since it was OT
yea, I've read that before in the thread. but never done it before. and the stuff around "autoyast.xml" I didn't understand exactly. has that to do with the tool "automatic install" ( or "Automatische Installation" in german; don't know the exact name in the english version) in YAST ? is there something in the documentation where u can point me to (I've got the boxed pro- version with the books of 9.3 if its in there .... ).
http://forgeftp.novell.com/yast/doc/SLES9/autoinstall/index.html There is a GUI tool in yast alled autoyast2-installation, that creates a core file you can then adapt following the above howto. Please install that rpm first and then go into yast --> misc autoinstallation, download my sample autoyast file from ftp://opensuse.linux.co.nz/pub/SUPER/files/autoyast.xml and load it in the autoyast installation tool. You could in theory just use that file, but then you can't log in. As a minimum without the gui tool you need to change ENCRYPTEDPASSWORD to for example txzvp3z2ZKYrc which equates to sles9 as password. I keep using that since I cannot be bothered to encrypt passwords the whole time. Change when you log in the first time. Current software selection is the default KDE system + kernel-source and gcc. Default partitioning in my xml file creates a 256 Mbyte /boot and a 3 GB / and 2048 Mb swap. You really should look at the XML and change things with vi or use the gui tool I mentioned and not just use the xml file alone. I turn this into a wiki entry or add it to the network install wiki entry ..... probably best in the next day or two. Regards, Andreas openSUSE is SUPER: To help in the SUSE Performance Enhanced Release project visit http://www.opensuse.org/index.php/SUPER
Andreas Girardet schrieb:
I changed the subject since it was OT
yea, I've read that before in the thread. but never done it before.
and
the stuff around "autoyast.xml" I didn't understand exactly. has that to do
with the
tool "automatic install" ( or "Automatische Installation" in german; don't know the exact name in the english version) in YAST ? is there something
in
the documentation where u can point me to (I've got the boxed pro-
version
with the books of 9.3 if its in there .... ).
http://forgeftp.novell.com/yast/doc/SLES9/autoinstall/index.html
There is a GUI tool in yast alled autoyast2-installation, that creates a core file you can then adapt following the above howto. Please install that rpm first and then go into yast --> misc autoinstallation, download my sample autoyast file from
ftp://opensuse.linux.co.nz/pub/SUPER/files/autoyast.xml
and load it in the autoyast installation tool. You could in theory just use that file, but then you can't log in. As a minimum without the gui tool you need to change ENCRYPTEDPASSWORD to for example
txzvp3z2ZKYrc
which equates to sles9 as password. I keep using that since I cannot be bothered to encrypt passwords the whole time. Change when you log in the first time. Current software selection is the default KDE system + kernel-source and gcc. Default partitioning in my xml file creates a 256 Mbyte /boot and a 3 GB / and 2048 Mb swap.
You really should look at the XML and change things with vi or use the gui tool I mentioned and not just use the xml file alone.
I turn this into a wiki entry or add it to the network install wiki entry ..... probably best in the next day or two.
Regards,
Andreas
openSUSE is SUPER: To help in the SUSE Performance Enhanced Release project visit http://www.opensuse.org/index.php/SUPER
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Andreas,
I have to say thanks again !! this will make my (testing)time realy
easier the next days !! but also a BIG THANKS to all others here,
on the list and the wiki, who worked out so mutch things in that short
time !!
some words when you edit the wiki for the network install:
first of all, I've tested the steps as you've written - they are both
working,
for the beta1 as also beta2 (and I think, beta3 will be ).
there is only one thing that need a short correction: when SLP wasn't
started
before, the service has to be started with "rcslpd start", esp. when openslp
was installed just before the first step.
and maybe some short hints for the ones who setup this stuff the first time:
- when SLP doen't work, the network install service can be reached on the
client by /
On Wed, Aug 24, 2005 at 2:44 am, in message <430B363C.5030508@addcom.de>, nordi@addcom.de wrote: Hi,
I've put up a page about preloading on openSUSE at [1]. This can drastically improve the startup time for some of the bigger applications. For example, my OpenOffice used to take 17 seconds. With preloading it only takes 6 seconds.
I would like to hear if/how it works on your systems, so go ahead and try it out! There is also a TODO list, so you can contribute if you want to.
Yes and my OpenOffice takes 4 seconds in conjunction with all the other improvements I have already put together;) http://www.opensuse.org/index.php/SUPER_standard_benchmark The chart describes each improvement I implemented seperately from each other based on a standard install. The last line is all improvements together ... and now my lappy flies .... I found a script that can help creating the file that defines what needs to be opened based on strace http://www.opensuse.org/index.php/10.0_beta2_i686_SUPER Hope this helps. I will put a report together today about my findings and send it to the list. Regards, Andreas openSUSE is SUPER: To help in the SUSE Performance Enhanced Release project visit http://www.opensuse.org/index.php/SUPER
participants (5)
-
Andreas Girardet
-
JBScout
-
Kashif Sheikh
-
nordi
-
Winston Graeme