Yes the file storage settings store the URL separately from conf_global. @Matt Can explain it and perhaps provide some instructions better than I can. We will have a little tool script you can use with the final release to make this kind of thing easier to quickly update
Performance in 4.0, as in 3.4, is something we continually improve with each release. The 4.0 you benchmarked is a lot better than the 4.0 of a few weeks or a few months ago. You may wish to enable MySQL datastore method rather than the default file system datastore if your main concern is memory/CPU usage. Please try that first and then wait until RC 1 and/or 4.0.0 final and see if there are improvements. Look forward to you reporting back
It's also for accessibility. By wrapping things in proper paragraph tags you are telling the browser "new paragraph now!" which, in turn, is telling that to search engines, screen readers, and so on. We chose to implement a certain amount of space between each paragraph using CSS that we though looked nice. You can certainly change that if, for some reason, you like your paragraphs all squished together.
The reason they are random is because zips are built on request based on what licenses you own and what you are upgrading. So it creates a temporary name as it builds the zip since it is possible multiple clients may request a zip at one time.
While we certainly value feedback but this approach: ... that really is not acceptable behavior. You made your point, others made a counter point who agreed with the way it is now. Your feedback is no more critical than anyone else's and we chose to go with the majority in this case who like it the way it is now as that's the way many other sites work their editors. Obviously if feedback changes from everyone we will revisit it but you cannot make it your personal vendetta as that is not an appropriate approach to feedback.
As usual we are looking at a whole lot more than this While the focus in this topic is all about one very specific, very narrow item there is a whole lot more going on. We are not going to just slap a change in without considering a broader scope. The search system in 4.0 is much more technically proficient than in 3.x. It also works very differently: so step 1 was to implement the new technology and now step 2 is to evaluate how we are using it. Obviously it has taken some real-world use to learn how best to implement things. As you can imagine, searching for "test" over and over on a staging site doesn't really give you a good feel for the best way to handle search .