GeoServer

Speed up JPEG output by avoiding RenderedImage cloning

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.7.0-beta1
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

Wroking around GEOS-2061 required cloning the image into a buffered one (to work around a bug in the jpeg writer). Simone thinks this can be improved to avoid the cloning, this jira issue acts as a reminder

Issue Links

Activity

Hide
Andrea Aime added a comment -

Is this one still valid? I think we have a better workaround in place?

Show
Andrea Aime added a comment - Is this one still valid? I think we have a better workaround in place?
Hide
Simone Giannecchini added a comment -

Not really
or better we have something better but I am not happy yet

Show
Simone Giannecchini added a comment - Not really or better we have something better but I am not happy yet
Hide
Andrea Aime added a comment -

We do the cloning only when strictly necessary. In those cases there does not seem to be any way around. Also the cloning is done in such a way that we end up sharing the data buffer so there should not be any particular issue remaining

Show
Andrea Aime added a comment - We do the cloning only when strictly necessary. In those cases there does not seem to be any way around. Also the cloning is done in such a way that we end up sharing the data buffer so there should not be any particular issue remaining
Hide
Andrea Aime added a comment -

Bulk closing all resolved issue that have not gotten any more feedback or comment in the last month

Show
Andrea Aime added a comment - Bulk closing all resolved issue that have not gotten any more feedback or comment in the last month

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: