hll memory estimate in MB instead of Bytes

[jshencode]

this drastically under estimate memory usage for hll query and cause out of memory situation during massive hll query hits, such as weekly hll contracts

[voyager-dw]

so originally we only reserved 10K for HLL? and now 10GB, isn't a little too bigger?

[jshencode]

yeah we have been reserved 10K.
10GB is to make sure each card only run one hll at a time since we cannot estimate hll effectively. We have agreed on 10G at the first place, but i think at some point the code got mixed up, MB changed to bytes. In production we have enough machines to spread out the large contract queries so that we don't see the problem. but in staging we can actually see the problem

[voyager-dw]

sure, we better do 2 observation:

1. how many real gpu memory allocated when running weekly hll contractor in production/staging
2. how it impacts production query when hll runs with 10GB reserved. Now as we under-reserve the memory, so other queries may still able to run. After we bump to 10G, other queries in the same machine will be totally blocked even the GPU might have spare space.

[codecov]

Codecov Report

Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (56108d0) 71.88% compared to head (6b14771) 71.89%.
Report is 47 commits behind head on master.

Files	Patch %	Lines
query/aql_processor.go	0.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff            @@
##           master     #312    +/-   ##
========================================
  Coverage   71.88%   71.89%            
========================================
  Files         166      166            
  Lines       23252    23367   +115     
========================================
+ Hits        16714    16799    +85     
- Misses       5246     5275    +29     
- Partials     1292     1293     +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.