After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 716150 - parallelize pipeline by running threads on striped regions
parallelize pipeline by running threads on striped regions
Status: RESOLVED FIXED
Product: shotwell
Classification: Other
Component: pipeline
unspecified
Other All
: Low enhancement
: 0.28
Assigned To: Shotwell Maintainers
Shotwell Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-05-24 07:38 UTC by Adam Dingle
Modified: 2017-11-11 13:54 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Charles Lindsay 2013-11-25 21:44:30 UTC


---- Reported by adam@yorba.org 2010-05-24 12:38:00 -0700 ----

Original Redmine bug id: 1964
Original URL: http://redmine.yorba.org/issues/1964
Searchable id: yorba-bug-1964
Original author: Adam Dingle
Original description:

This could be a big performance win and might be doable for 0.6, even.



---- Additional Comments From shotwell-maint@gnome.bugs 2010-06-03 16:52:00 -0700 ----

### History

####

#1

Updated by Adam Dingle over 3 years ago

  * **Priority** deleted (<strike>_High_</strike>)

Off the table for 0.6.



--- Bug imported by chaz@yorba.org 2013-11-25 21:44 UTC  ---

This bug was previously known as _bug_ 1964 at http://redmine.yorba.org/show_bug.cgi?id=1964

Unknown Component 
   Using default product and component set in Parameters 
Unknown version " in product shotwell. 
   Setting version to "!unspecified".
Unknown milestone "unknown in product shotwell. 
   Setting to default milestone for this product, "---".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Resolution set on an open status.
   Dropping resolution 

Comment 1 Jens Georg 2016-11-04 11:32:55 UTC
Or shove it into GLSL or use GEGL
Comment 2 Jens Georg 2017-11-11 13:54:48 UTC
This problem has been fixed in the unstable development version. The fix will be available in the next major software release. You may need to upgrade your Linux distribution to obtain that newer version.