You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Chart generation is a very powerful feature, but it is generated for every question, despite being most of the time not necessary. It can be an issue when the app is used on large datasets, because the chart generation is then very long and consumes a lot of tokens.
The first solution used to adress this problem (VannaBase.should_generate_chart) already narrows the amount of unnecessary chart generation, but there is in my opinion a much simplier solution to this issue: make the chart generation user-triggered. This would mean adding a button Generate graph after the SQL query has succeeded.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Chart generation is a very powerful feature, but it is generated for every question, despite being most of the time not necessary. It can be an issue when the app is used on large datasets, because the chart generation is then very long and consumes a lot of tokens.
The first solution used to adress this problem (
VannaBase.should_generate_chart
) already narrows the amount of unnecessary chart generation, but there is in my opinion a much simplier solution to this issue: make the chart generation user-triggered. This would mean adding a buttonGenerate graph
after the SQL query has succeeded.Beta Was this translation helpful? Give feedback.
All reactions