riflerrick / b2 Goto Github PK

Currently run phase only supports single insert/update/delete and select. Support for bulk insert/delete/update required

currently in case APPROX_TABLE_SIZE is not given, select count is performed on the table which is highly inefficiently. a better fallback would be to use information_schema.tables more specifically:

select TABLE_ROWS from information_schema.tables where table_schema="helloworld" and table_name="ilapahsi"

This can be done using go-templates. normalized queries can be provided by the user, getQuery will no longer be used to generate queries, follow (this)[https://golang.org/pkg/text/template/] for reference

Since go leverages message passing, locks should be avoided if possible. Enhancement required in sharing metadata using message passing rather than using locks

the config environment variables that were used are:

      - TIME_SERIES_TICK_MS=1000
      - METRIC_POLL_TICK_MS=1000
      - TEMP_TABLE_PREP_SIZE_RATIO=0.10
      - PREP_PHASE_CHUNK_SIZE=1000000
      - TEMP_TABLE_RUN_SIZE_RATIO=0.10
      - RUN_PHASE_PUBLISH_CHUNK_SIZE=10000
      - RUN_PHASE_PUBLISH_SLEEP_TIME=200
      - APPROX_TABLE_SIZE=102157035

In case the RPM is given a low value, the number of instances going to a negative value. The most probable cause of this would be that the rate at which new instances are created because of the number of instances going zero is actually less than the rate at which instances are getting downscaled due to RPM