On 1/25/19 2:42 PM, Michal Kubecek wrote:
No. It's not about "optimizations". It's about choices like which services we want to start by default. Which modules to load on boot. If we want to setup firewall by default. Maybe also how long timeout we want for the boot menu. (I sincerely hope he does not count _that_ into the "boot time" but I wouldn't be really surprised.)
As an extreme, we could drop everything except what is necessary to get a login prompt by default and we would get super fast "boot time in default install". On the other hand, our users would get quite angry that they have to enable all kind of services (including those they had no idea they need) to make their system usable. Is it what you want?
So what you are saying is, you would not want to see the default configuration, as found in a clean install, to be benchmarked. You want specific changes to that configuration for better performance. Is that right? Am I reading you correctly? If so, *that is optimizing the system*. "Optimizing", in the context of benchmarking software performance, means "making specific changes to improve performance". Turning stuff off to make it faster than the default config _is optimizing it_.
That's just sad.
Then I am afraid that you are not going to like the entire world of performance testing.
Even more sad that you still believe what you said above after having some experience.
How else would you do it? Seriously. I have worked for some 15 different computer magazines and websites in Britain, Germany, America and other countries. I used to be the editor of Heise UK, for example. This is how Heise works. This is how benchmarking works. What would you change? -- Liam Proven - Technical Writer, SUSE Linux s.r.o. Corso II, Křižíkova 148/34, 186-00 Praha 8 - Karlín, Czechia Email: lproven@suse.com - Office telephone: +420 284 241 084 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org