Getting the most out of Notes 8 Standard - Pt 2
Of all the changes you can make to your Notes 8 client environment that will make it "feel" faster, probably the most effective one is to change the launch time of the productivity apps. By default, they are set to launch with the client, which means when you start Notes, you're also waiting for the productivity apps to cache in the background.
You can turn off the pre-load altogether. Or you can link it to your OS launch, which is what I started doing since yesterday. I haven't noticed any change in launch performance.
UPDATE: On further examination, I'm not sure the "on operating system launch" actually does anything. I can't find anything in my Services, in my registry, or in the Windows Startup group to indicate. Even going old-school and checking SYSEDIT revealed no identifiable settings associated with anything in my Notes 8 folder.
IBMers, feel free to chime in here with any feedback on this setting.
UPDATE 2: Well, soffice.exe definitely starts on the OS start. It doesn't seem to accelerate the Notes 8 client itself, but it definitely makes the productivity apps load faster.
I should hasten to add that although I seem to be able to get the Notes 8 client to launch in < 60 seconds after a reboot, and < 20 seconds once it's already been run, the control of the productivity editor launch doesn't seem to change Notes 8 itself whether I load on OS, or don't pre-load at all. The main thing is NOT to pre-load at Notes launch time.
One interesting thing: a colleague here running Vista is reporting that his initial launch and re-start times are pretty much identical. This makes sense if you're familiar with Vista's pre-caching of commonly used applications. As soon as he starts the OS, it caches the application files for Notes 8, in accordance with Vista's app acceleration techniques.
Stay tuned!
Comments
Posted by Steve At 09:30:47 AM On 09/10/2007 | - Website - |
Take a look at javaw.exe in the task manager.
If it works its about the loading of the plug-ins of the Eclipse environment and Eclipse as Expeditor do consist mostly of plug-ins. Eclipse has quite a fancy mechanism to load those plug-ins lazily. Of course lazy loading might cause strange freezes when for a certain tasks suddenly a bunch of plug-ins are loaded lazily. So preloading might offer a nicer user-experience. Of course you pay with app start up time. If it works, start when OS starts appears as the best option.
Eclipse 3.3 creates a eclipse.exe task. I am quite sure that it was javaw in earlier versions.
regards
Axel
Posted by Axel Janssen At 11:45:44 AM On 09/17/2007 | - Website - |