Hi Utomo, Andrew, On Thu, Nov 02, 2006 at 11:07:06AM +0700, Utomo wrote: > > My original idea was. > To make Ooo faster opening the Microsoft Office files. (but without adding > memory usage by OOo) > Especially for user with old computer, such as PIII with around 128 memory > (which now mostly suffer from the huge memory usage by Ooo, and they feel > very long time opening the Microsoft office files).
Just take http://blogs.sun.com/GullFOSS/entry/performance_gain_of_factor_15 as an example. It surely increses performance significantly - but only for a small part of the documents out there... How would you compare that to other improvements? > [...] > (I will provide some test file when the bounty start.) Yes, for file-open/save improvements this is a must. > -----Original Message----- > From: Andrew Douglas Pitonyak [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 02, 2006 10:35 AM > To: [email protected] > Subject: Re: [dev] Bounty for performance improvements Please don't fullquote. > Utomo wrote: > [...] > Performance should be quantified and explained by the submitter. In > other words, the submitter should indicate how to test and demonstrate a > speed improvement. See above. Surely is an improvement, but... > Memory and runtime both sounds like improvements to me. > > Broader impact should carry more weight. ...how will you weight different improvements? > For example, a 100% improvement > in sort speed is probably not as important as a 10% improvement in > screen redraw time because the screen is almost always updated. By the > same token, a 10% improvement in screen redraw may also beat a 20% > improvement in macro run-time. Sure: But the problem is: How do you map this to the amount of money the improvement is "worth"? > I would probably use imprecise statements as those, and then after some > prioritizing, leave the final decision to public voting if it is not > obvious as to the final winner, or simply decide up front, that public > voting will be done. A Bounty is not a contest usually. It is an offer to pay an (mostly symbolic) amount of money for a contribution. Some people show interest and once somebody says: OK, I'm taking the challenge, I will work on it, the bounty is marked as "in the works", so that other people know that when they start something they might not get the bounty because already the person who was there first will get it (once he is finished and claims the bounty). Sure, you can do performance optimizations in multiple areas, but the question is whether the one offering the money is willing to pay for more than one improvement... ciao Chrtistian -- NP: Metallica - Better Than You --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
