deemoliu opened a new pull request #8108:
URL: https://github.com/apache/pinot/pull/8108


   Per #6729, add a tool to estimate heap usage for upsert table keySpace and 
valueSpace
   
   Calculated keySpace by the following formula
   
   UpsertFrequency = 1 - (nums of records / nums of skipUpsert records).
   unqiue Keycombination = messageRate * retentionValue * (1 - upsertFrequency).
   KeySpace = bytesPerKey * uniqueCombinations
   ValueSpace = bytesPerValue * uniqueCombinations
   
   ***************************************************
   Estimated heap usage for the table
   EstimateHeapSize -tableName meetupRsvp -schemaFile meetupRsvp_schema.json 
-tableConfigFile meetupRsvp_realtime_table_config.json -messageRate 1000
   schema file          
/var/folders/dr/xqtm8ycd4fq6fctr4vkz37th0000gn/T/1643757837546/meetupRsvp/meetupRsvp_schema.json
   table config file            
/var/folders/dr/xqtm8ycd4fq6fctr4vkz37th0000gn/T/1643757837546/meetupRsvp/meetupRsvp_realtime_table_config.json
   column stats         8
   bytes per key                8
   bytes per value              64
   message rate per second              1000.0
   retention            1DAYS
   nums of record               12
   nums of record (skipUpsert)          12
   Upsert frequency             1.0
   Estimated total key space (GB)               0.64373016
   Estimated total value space (GB)             5.1498413
   
   
   ## Description
   <!-- Add a description of your PR here.
   A good description should include pointers to an issue or design document, 
etc.
   -->
   ## Upgrade Notes
   Does this PR prevent a zero down-time upgrade? (Assume upgrade order: 
Controller, Broker, Server, Minion)
   * [ ] Yes (Please label as **<code>backward-incompat</code>**, and complete 
the section below on Release Notes)
   
   Does this PR fix a zero-downtime upgrade introduced earlier?
   * [ ] Yes (Please label this as **<code>backward-incompat</code>**, and 
complete the section below on Release Notes)
   
   Does this PR otherwise need attention when creating release notes? Things to 
consider:
   - New configuration options
   - Deprecation of configurations
   - Signature changes to public methods/interfaces
   - New plugins added or old plugins removed
   * [ ] Yes (Please label this PR as **<code>release-notes</code>** and 
complete the section on Release Notes)
   ## Release Notes
   <!-- If you have tagged this as either backward-incompat or release-notes,
   you MUST add text here that you would like to see appear in release notes of 
the
   next release. -->
   
   <!-- If you have a series of commits adding or enabling a feature, then
   add this section only in final commit that marks the feature completed.
   Refer to earlier release notes to see examples of text.
   -->
   ## Documentation
   <!-- If you have introduced a new feature or configuration, please add it to 
the documentation as well.
   See 
https://docs.pinot.apache.org/developers/developers-and-contributors/update-document
   -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org
For additional commands, e-mail: commits-h...@pinot.apache.org

Reply via email to