tree 8a8f6798ce109869525b77863819a65dcdfdd9c2
parent 60a4d7fab17033334dceea27d5ae708286002d4a
author chiyotsai <chiyotsai@google.com> 1565219547 -0700
committer Chi Yo Tsai <chiyotsai@google.com> 1565280878 +0000

Don't allocate hash_me memory for BLOCK_4X4 on 4K+

On high resolution long video sequences, the memory consumption is
dominated by the hash table used for screen content motion estimation.

Since 4K+ videos don't go to BLOCK_4X4, we don't need to store the hash
table at this level. This reduces the memory consumption of hash_me by
~1/6, which is about 835MBs, or ~10% of heap memory when encode 17
frames.

BUG=aomedia:2453

Change-Id: Ic7f4104ac55d802193444b16232ff4d48c3bf2ea