google bigquery - Why standard SQL UDF increase the Bytes billed so much for all the query after it? -

bq support team,

we investigate standard sql udf in bq, , seems works pretty good. noticed can costly use it. bytes billed can hundred times original table. think makes sense udf make need memory process. not understand queries use table generated udf sql still use memory udf sql. our original table 1.03k, , udf sql run has 10m billed. , below job info normal query:

select * project.udf_sql_table_name;

job id          * creation time   apr 14, 2017, 2:57:29 pm start time      apr 14, 2017, 2:57:29 pm end time        apr 14, 2017, 2:57:30 pm bytes processed 1.05 kb bytes billed    10.0 mb billing tier    1 destination table   * use legacy sql  fase 

from job info, can see udf sql generate table 1.05k, saved project.udf_sql_table_name. , simple "select", "bytes billed" still 10m, 1000 times bigger processed table. may know correct when using udf? thanks

the "bytes billed" still 10m, 1000 times bigger processed table. ... correct?

yes. correct. see on-demand pricing

charges rounded nearest mb, minimum 10 mb data processed per table referenced query, , minimum 10 mb data processed per query.