title: Drawing paths and hardware acceleration
body: <p>I'm drawing a rather large path in my view and I'm running into some performance problems. The path is currently 32,000 points long, but my application should scale to at least 128,000 points. I can't really do anything about the size of the path, as the datasets are just that large and I need to be able to display the whole path at once and allow zooming in.</p>
  
  <p>I'm using a Nexus 10 running Android 4.2, which has hardware acceleration enabled by default for applications that don't explicitly disable it.</p>
  
  <p>The path is created with the following code (I omitted some setup and other irrelevant parts):</p>
  
  <pre><code>dataPath.moveTo(0, offset - (float) data[leftLimit]/ scalingFactor);
          for (int i = leftLimit; i &lt; rightLimit; ++i) {
              x = (i - leftLimit) * dx;
              y = offset - (float) data[i]/ scalingFactor;
              dataPath.lineTo(x, y);
          }
  </code></pre>
  
  <p>And then drawn in the <code>onDraw()</code> method:</p>
  
  <pre><code>canvas.drawColor(Color.WHITE);
  canvas.drawPath(dataPath, linePaint);
  </code></pre>
  
  <p>I measured the time it takes to draw my view using <code>adb shell dumpsys gfxinfo</code> with and without hardware acceleration, and to my suprise the hardware acceleration is much slower:</p>
  
  <p><strong>With hardware acceleration:</strong></p>
  
  <p><img src="https://i.stack.imgur.com/AmhBB.png" alt="enter image description here"></p>
  
  <p><strong>Without hardware acceleration:</strong></p>
  
  <p><img src="https://i.stack.imgur.com/NbOWa.png" alt="enter image description here"></p>
  
  <p>The hardware accelerated version takes around 200-300 ms per frame, most spent in the Process stage. The non-accelerated version takes around 50 ms, with 2/3 in the Draw stage and 1/3 in the process stage.</p>
  
  <p>Obviously even my faster version without hardware acceleration is still too slow to achieve 60 fps, or to be even barely useable when I move to larger datasets. </p>
  
  <p>The idea to render the path to a bitmap and then only transform that bitmap to fit the screen is also problematic in my case. I need to support zooming in very far onto the path, and to enable zooming in without the path quality getting much worse I would have to render oversized bitmaps of the path (and would likely run into memory limits and the texture size limits). And when zooming in far I would have to either create newer images of only parts of the path, or switch to just rendering the path directly, which likely would lead to delays greater than the framerate if the performance is still similar to what I have right now.</p>
  
  <p>What I'm wondering now is</p>
  
  <ul>
  <li>Is drawing lines/paths just something the GPU is bad at and that one should not try to hardware accelerate, or am I likely doing something wrong that causes the bad performance?</li>
  <li>Is there anything I can do to draw such huge paths with acceptable performance?</li>
  </ul>