Skip to content
Snippets Groups Projects
Select Git revision
  • main default protected
  • blm_dev_chan
  • release/1.4.0 protected
  • widgets_draw
  • return_of_melodic_demo
  • task_cleanup
  • mixer2
  • dx/fb-save-restore
  • dx/dldldld
  • fpletz/flake
  • dx/jacksense-headset-mic-only
  • release/1.3.0 protected
  • fil3s-limit-filesize
  • allow-reloading-sunmenu
  • wifi-json-error-handling
  • app_text_viewer
  • shoegaze-fps
  • media_has_video_has_audio
  • fil3s-media
  • more-accurate-battery
  • v1.4.0
  • v1.3.0
  • v1.2.0
  • v1.2.0+rc1
  • v1.1.1
  • v1.1.0
  • v1.1.0+rc1
  • v1.0.0
  • v1.0.0+rc6
  • v1.0.0+rc5
  • v1.0.0+rc4
  • v1.0.0+rc3
  • v1.0.0+rc2
  • v1.0.0+rc1
34 results

mp_uctx.c

  • dx's avatar
    3fde04ab
    Revert ctx to previous version from 2024-03-11 · 3fde04ab
    dx authored
    There was a performance regression since then, probably located in these upstream commits:
    
    * 720a5357 "rasterizer: always do at least one subidvision of beziers" - 15% FPS drop on sensors app
    * 5b4d3d44 "ctx: the glyph API now takes glyph_ids and not unicode codepoints" - further 25% FPS drop on sensors app
    
    Not terribly sure about the last commit because it doesn't work by itself (most glyphs don't render, this was fixed later in b5a9a81d), but it's most likely the group started by that one.
    
    These commits happened to be 2-3 days after our last known good commit, and performance of the sensors app remained stable for months afterwards.
    
    Because we're preparing for a release and pippin doesn't seem to have the time to address this right now, and I'd have no idea where to even begin, I'm doing the next best thing I know and reverting to the known good version.
    3fde04ab
    History
    Revert ctx to previous version from 2024-03-11
    dx authored
    There was a performance regression since then, probably located in these upstream commits:
    
    * 720a5357 "rasterizer: always do at least one subidvision of beziers" - 15% FPS drop on sensors app
    * 5b4d3d44 "ctx: the glyph API now takes glyph_ids and not unicode codepoints" - further 25% FPS drop on sensors app
    
    Not terribly sure about the last commit because it doesn't work by itself (most glyphs don't render, this was fixed later in b5a9a81d), but it's most likely the group started by that one.
    
    These commits happened to be 2-3 days after our last known good commit, and performance of the sensors app remained stable for months afterwards.
    
    Because we're preparing for a release and pippin doesn't seem to have the time to address this right now, and I'd have no idea where to even begin, I'm doing the next best thing I know and reverting to the known good version.