Basically, the prebinding process just creates some kind of a "roadmap" which shows the system which application uses which libraries. Once an application is started, the system looks into this roadmap and loads the needed libraries into the RAM. Now, if you installed stuff and moved some files around, it can happen that this roadmap gets outdated. So once you launch an application, the system cannot immideately find a needed librarie and has to search it. However, with updated prebindings, this doesn't happen. I heard that one of the reasons 10.1 application startup times is that it loads most of the libraries into RAM at startup...if this is true, we just might need some more RAM.
If you install new software in OS X, like updates to the system, there is the final step "optimizing the system". In this step, the prebindings are updated. So installing DevTools 10.0.0 or any X update might give you the feel of a small speed increase which will vanish after some time without regularly updated prebindings. DevTools 10.0.1 however changed some graphic libraries and in fact it speeded up some Aqua elements...although the speed increase is far from beeing as dramatic as what was shown with 10.1 at wednesday.
So what you can do: Install DevTools 10.0.1
REGULARLY update your prebindings:
You can do this easily with a tool called XOptimize (search it in version-tracker.com) or just gain root-access and type
update_prebindings -root / in the console, with the -verbose option if you wanna see what's going on.
Also, there is a tool which manages all the logfiles and stuff like that, which can bring another very small speed increase if it is used regularly. It basically just runs maintainance scripts which are executed daily, weekly and monthly from OS X, but only if the Mac is turned on at the critical time where the script SHOULD run (for example at midnight). I don't recall the name of the tool but I am sure the others in this forum will post the name.
excuse my bad english
ulrik