Many customers on Statsig run hundreds of concurrent experiments. On Warehouse Native, this means that interactive queries from the Statsig console can run slowly during peak hours for daily compute
Now, users on Snowflake, Databricks, and Bigquery can specify separate compute resources for 'interactive' console queries vs. scheduled 'job' queries - meaning the interactive queries will always be snappy. This also means a large compute resource used for large-scale experiment analysis won't get spun up when running small interactive queries like loading data samples.
For those warehouses, we've also added the ability to specify different service accounts for different "Statsig Roles" within the Statsig roles system. This means that the scorecard service account has the necessary access to user data for calculating experiment results, but customers can specify privacy rules like masking for sensitive fields to prevent access to sensitive data through interactive queries in the Statsig console.