Re: A brief on the focus on Performance improvements in Evolution 2.8 for GNOME 2.16
On Wed, 2006-09-06 at 00:40 +0200, Claus Schwarm wrote: > Hi, > > thanks for the text and especially for the images. I tried to re-write > it a little bit to make the text a little bit less demanding. > My first try is available here: > > http://live.gnome.org/TwoPointFifteen/ReleaseNotes/TwoSixteenPerformance > > I probably over-simplyfied too much. Please have a look and let me know > where it happened. That would be a real help. No. I think you have done a wonderful job - the text looks more like human-speak and less geekish. And, it does adequately represent what I wanted to convey. Thanks, Harish -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: A brief on the focus on Performance improvements in Evolution 2.8 for GNOME 2.16
Hi, thanks for the text and especially for the images. I tried to re-write it a little bit to make the text a little bit less demanding. Unfortunatly, I probably not a developer myself so I had to guess wildly about the meaning of some notes. For example, I totally failed to understand the sentence about the GroupWise backend for Evolution data center. My first try is available here: http://live.gnome.org/TwoPointFifteen/ReleaseNotes/TwoSixteenPerformance I probably over-simplyfied too much. Please have a look and let me know where it happened. That would be a real help. Btw, rocking images! Thanks. :-) Cheers, Claus On Tue, 05 Sep 2006 12:46:17 +0530 Harish Krishnaswamy <[EMAIL PROTECTED]> wrote: > Please find attached a HTML file with a few bullet points and a few > graphs on what exactly was done on the performance front, in the > Evolution 2.7 development cycle. > > Hope you find this useful. Let me know if you would like to have > more/different information. > > Thanks, > Harish > -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: Epiphany release notes
Hi, Reinout! On Tue, 5 Sep 2006 09:01:26 +0200 "Reinout van Schouwen" <[EMAIL PROTECTED]> wrote: > > Or "Epiphany now uses the latest technology from Mozilla.org to let > you check the spelling of text entered in the web browser. The spell > checker needs a Firefox 2.0 (or equivalent) back-end to work." > > Sounds better? I don't think we should be getting any deeper into > technical details... > It may sound better -- well, more cooperate like, IHO ;-) -- but it detracts readers by letting them read ten words of uninteresting information without a good reason. I don't think they care much what Epiphany uses. They want to know what additional benefits GNOME 2.16 provides for them. Thus, I'd like to keep the 'You can now ...' approach. > > Well, I can see how it's reasonable to allocate more space to > components with more visible new features. It's just that web > publishing space is cheap :) However the release notes should not be > so long that people give up reading half way. Do you think that would > be the case? > I believe that the majority of readers will already give up after the third page. Maybe they will read a forth page if I can find a good description of performance improvements. Of course, I'm not really sure about it -- a statistic would help. But I'm quite sure that nearly 99.99% of all readers will have forgotten what made this GNOME release different to the ones before within three days. If we're lucky they will remember the major headlines: "Eye candy, feature improvements, usability improvements, etc." but, honestly, I think this will only work if we keep the headlines for the next releases. As a test: Just try to remember what was the most important post on planet.gnome.org three days ago. Or as a different one: Can you remember what you eat for breakfast three days ago? ;-) See? Your breakfast was something you could see, small, and taste; it was no abstract description. Still, most people have problems remembering it immediately. The details of our release notes will be forgotten within hours. If we're really lucky readers will somehow have the impression that they have made the right decision by using GNOME, or that they should give GNOME another try the next time. That's the best we can hope for. > > important. Since I have problems to understand the first item in > > your release notes, I'm only good enought to represent an outsider > > point of view. > > OK, so maybe that part needs rephrasing too. What it means is that, in > contrast to previous versions, the back-button-history is preserved > in a new tab or window when you open it from a link on some webpage. > Say that you've visited sites A, B and C and are now viewing site X. > Site X contains a link to site Y but you decide you'd rather view > site Y in a different tab. You could copy the Y address to the > clipboard, paste it in the address bar and press Ctrl+enter to have > it open in a new tab (this functionality was polished in 2.16 too, by > the way). Then the history under the Back button for site Y is empty. > But you could also right click the link to Y and select 'Open in new > tab'. Then sites A, B and C will now be available in the back-history > of site Y as well as site X. > This is tricky. I would suggest: "You can now continue to use the history of the originating website if you open the next website in a new tab: the full history will still be available under the 'back' button, for both tab windows." If you need a short description for gnomefiles, write something about "better history navigation" or so. Cheers, Claus -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
A brief on the focus on Performance improvements in Evolution 2.8 for GNOME 2.16
Please find attached a HTML file with a few bullet points and a few graphs on what exactly was done on the performance front, in the Evolution 2.7 development cycle. Hope you find this useful. Let me know if you would like to have more/different information. Thanks, Harish Performance and Memory optimizations in Evolution 2.8 : Evolution IMAP : Do not fetch all HEADERS. Only fetch a minimal functional subset of Headers. This resulted in a reduction of initial header loading time by about 48%, against Evolution 2.6. See Fig. IMAP Headers Load Time. GroupWise : Comparison of item_ids during server synchronization operations reduced to O(n) from O(n^2) , thereby eliminating frequent CPU spikes during periodic refresh operations. Evolution Data Server Reduction of memory footprint : Multiple copies of libical not statically linked to the providers anymore. This cuts down primary memory requirements by around 600 KB. Allow dynamic linking to system db GroupWise – split the provider cache by components (Calendar/Tasks/Memos) ensuring only one copy of the item exists in cache. Reduces memory used by the GW provider by 66%. GroupWise backend : Loading of Tasks into the cache during account creation reduced by about 80% . See Graph – Tasks Loading. And to let you know that this is not optimization just for the sake of itself but a trade-off for better user experience... With Smarter sequencing of GroupWise Calendar pre-load in Evolution 2.8, it takes longer to fetch all items into the cache overall (See Graph : Calendar Loading Time) but the overall user experience (measured by the time taken to load/display events closer to current date) improved by a whopping 94% in average. evoperformanceformarketing_html_71baac1e.gif Description: GIF image evoperformanceformarketing_html_m3d90fa27.gif Description: GIF image evoperformanceformarketing_html_m22de1aa3.gif Description: GIF image evoperformanceformarketing_html_m5559c5ad.gif Description: GIF image -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
Re: Epiphany release notes
Hi Claus, Op di, 05-09-2006 te 01:23 +0200, schreef Claus Schwarm: > No mentioning of Firefox. Maybe we can use the following line in the > release notes? > > "You can now check the spelling of the text entered in the Epiphany web > browser, when it is built with a Firefox 2.0 (or equivalent) > back-end." Or "Epiphany now uses the latest technology from Mozilla.org to let you check the spelling of text entered in the web browser. The spell checker needs a Firefox 2.0 (or equivalent) back-end to work." Sounds better? I don't think we should be getting any deeper into technical details... > Btw, Epiphany is mentioned a second time in the backends section as one > of the GNOME applications that switched to the new printing dialog. Right, I hadn't noticed that. > I know I won't make friends with the next sentence but honestly: I see > no reason to give Epiphany more space in the release notes *this > time*. :-( Well, I can see how it's reasonable to allocate more space to components with more visible new features. It's just that web publishing space is cheap :) However the release notes should not be so long that people give up reading half way. Do you think that would be the case? > important. Since I have problems to understand the first item in > your release notes, I'm only good enought to represent an outsider > point of view. OK, so maybe that part needs rephrasing too. What it means is that, in contrast to previous versions, the back-button-history is preserved in a new tab or window when you open it from a link on some webpage. Say that you've visited sites A, B and C and are now viewing site X. Site X contains a link to site Y but you decide you'd rather view site Y in a different tab. You could copy the Y address to the clipboard, paste it in the address bar and press Ctrl+enter to have it open in a new tab (this functionality was polished in 2.16 too, by the way). Then the history under the Back button for site Y is empty. But you could also right click the link to Y and select 'Open in new tab'. Then sites A, B and C will now be available in the back-history of site Y as well as site X. regards, -- Reinout van Schouwen -- marketing-list mailing list marketing-list@gnome.org http://mail.gnome.org/mailman/listinfo/marketing-list
