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 ServerReduction of memory footprint :
GroupWise backend :
And to let you know that this is not optimization just for the sake of itself but a trade-off for better user experience...
|
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