Difference between revisions of "Activities/Thumbs View in Journal"

From Sugar Labs
Jump to navigation Jump to search
Line 50: Line 50:
 
! len(gc.objects())
 
! len(gc.objects())
 
|-
 
|-
| 311m 42m
+
| 252m 25m
| 121m 14m
+
|
 +
|
 +
| 33757
 +
|-
 +
| 319m 48m
 +
| 120m 14m
 
| 113m 12m
 
| 113m 12m
| 47017
+
| 53116
 
|-
 
|-
| 330m 58m
+
| 320m 48m
| 121m 14m
+
| 120m 14m
| 132m 31m
+
| 113m 12m
| 54184
+
| 56065
 
|-
 
|-
| 330m 58m
+
| 320m 48m
| 121m 14m
+
| 120m 14m
| 146m 45m
+
| 113m 12m
| 55595
+
| 56964
 
|-
 
|-
| 333m 61m
+
| 320m 48m
| 121m 14m
+
| 120m 14m
| 160m 59m
+
| 113m 12m
| 56798
+
| 60262
 
|-
 
|-
| 336m 64m
+
| 320m 49m
| 121m 14m
+
| 120m 14m
| 173m 72m
+
| 113m 12m
| 57619
+
| 60786
 
|-
 
|-
| 335m 63m
+
| 321m 49m
| 121m 14m
+
| 120m 14m
| 191m 90m
+
| 113m 12m
| 58722
+
| 62339
 
|-
 
|-
| 346m 75m
+
| 321m 50m
| 121m 14m
+
| 120m 14m
| 204m 103m
+
| 113m 12m
| 60885
+
| 62833
 
|-
 
|-
| 347m 75m
+
| 323m 52m
| 121m 14m
+
| 120m 14m
| 215m 114m
+
| 113m 12m
| 62155
+
| 65256
 
|-
 
|-
| 349m 77m
+
| 325m 53m
| 121m 14m
+
| 120m 14m
| 226m 125m
+
| 113m 12m
| 63911
+
| 65450
|-
 
| 349m 77m
 
| 121m 14m
 
| 243m 142m
 
| 64719
 
 
|-
 
|-
| 341m 69m
+
| 324m 53m
| 121m 14m
+
| 120m 14m
| 256m 154m
+
| 114m 13m
| 65227
+
| 66252
 
|-
 
|-
| 344m 72m
+
| 325m 53m
| 121m 14m
+
| 120m 14m
| 269m 168m
+
| 114m 13m
| 66589
+
| 66820
 
|-
 
|-
 
|}
 
|}

Revision as of 08:37, 27 August 2009


Summary

Add thumbs view to Journal.

Owner

Current status

  • Targeted release: 0.86
  • Last updated: Sat Aug 22 12:37:36 UTC 2009
  • Percentage of completion: 75%

Detailed Description

Implement thumbs view mockup.

Thumbs.png

Benefit to Sugar

In process..

Scope

  • shell code

Implementation

Memory usage with thumbs

Scroll and requery thumbs view during 10 min.
(for huge ds memory consumption see #1240)

sugar-session sugar-presence-service datastore-service len(gc.objects())
252m 25m 33757
319m 48m 120m 14m 113m 12m 53116
320m 48m 120m 14m 113m 12m 56065
320m 48m 120m 14m 113m 12m 56964
320m 48m 120m 14m 113m 12m 60262
320m 49m 120m 14m 113m 12m 60786
321m 49m 120m 14m 113m 12m 62339
321m 50m 120m 14m 113m 12m 62833
323m 52m 120m 14m 113m 12m 65256
325m 53m 120m 14m 113m 12m 65450
324m 53m 120m 14m 114m 13m 66252
325m 53m 120m 14m 114m 13m 66820

Memory usage without thumbs

Scroll and requery list view(from trunk) during 10 min.

sugar-session sugar-presence-service datastore-service len(gc.objects())
251m 24m 33751
314m 44m 121m 14m 114m 13m 51101
315m 44m 121m 14m 115m 14m 53334
315m 45m 121m 14m 116m 15m 56375
315m 45m 121m 14m 116m 15m 59084
318m 48m 121m 14m 117m 16m 63172
320m 50m 121m 14m 118m 17m 67776
323m 53m 121m 14m 119m 18m 72693
325m 55m 121m 14m 121m 20m 76193
326m 56m 121m 14m 122m 21m 78869
328m 58m 121m 14m 123m 22m 81449
329m 59m 121m 14m 124m 23m 84480

How To Test

This does not need to be a full-fledged document. Describe the dimensions of tests that this feature is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be.

Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.

A good "how to test" should answer these four questions:

  • What special hardware / data / etc. is needed (if any)?
  • How do I prepare my system to test this feature? What packages need to be installed, config files edited, etc.?
  • What specific actions do I perform to check that the feature is working like it's supposed to?
  • What are the expected results of those actions?

User Experience

If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.

Dependencies

Just regular glucose dependencies.

Contingency Plan

None necessary, revert to previous release behaviour.

Documentation

Release Notes

The Sugar Release Notes inform end-users about what is new in the release. An Example is 0.84/Notes. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.

Comments and Discussion