You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "iercan (via GitHub)" <gi...@apache.org> on 2025/01/11 11:32:10 UTC
[I] Performance issues after migration from 2.1.1 causing by pivot tables [superset]
iercan opened a new issue, #31799:
URL: https://github.com/apache/superset/issues/31799
### Bug description
We are using superset 2.1.1. We wasn't able to upgrade it since this version because we were experiencing performance issues on some dashboards(slow reactions and sometimes crashes).
After further investgations we have detected this is causing by pivot table migration. All problematic dashboards had some legacy pivot tables. I'm opening this issue aiming to help anyone experiencing same issue because we also have a workaround.
**How to reproduce.**
1. Create a dashboard that has at least 4-5 legacy pivot table on version 2.1.1. (Our charts had 10000 row limit but I'm not sure this is relevant)
2. Migrate superset after any version bigger than 3.0.0
**Workaround**
As a workaround we just save and overwrite these charts and problem has gone.
### Screenshots/recordings
_No response_
### Superset version
master / latest-dev
### Python version
3.9
### Node version
16
### Browser
Chrome
### Additional context
_No response_
### Checklist
- [X] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [X] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
--
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: notifications-unsubscribe@superset.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Performance issues after migration from 2.1.1 causing by pivot tables [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #31799:
URL: https://github.com/apache/superset/issues/31799#issuecomment-2588029985
When you say "The issue was resolved by saving and overwriting the affected charts." do you mean that after saving them with the newer (currently supported) pivot chart, the performance problems went away? Also, what version are you running now, is it a 4.x variant? Is there any remaining issue after overwriting the charts? Trying to figure out how to reproduce this issue or what we can do to move it forward.
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Performance issues after migration from 2.1.1 causing by pivot tables [superset]
Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #31799:
URL: https://github.com/apache/superset/issues/31799#issuecomment-2591302813
Weird. I'm not sure what the Save process would change, but there must be _something_ in the form data that wasn't migrated properly. I wonder if @michael-s-molina or @villebro have any idea. I haven't heard of this one happening to others, so I wonder if there IS a migration that's failing for some unforeseen reason.
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Performance issues after migration from 2.1.1 causing by pivot tables [superset]
Posted by "iercan (via GitHub)" <gi...@apache.org>.
iercan commented on issue #31799:
URL: https://github.com/apache/superset/issues/31799#issuecomment-2589116154
@rusackas
> When you say "The issue was resolved by saving and overwriting the affected charts." do you mean that after saving them with the newer (currently supported) pivot chart, the performance problems went away?
We opened the "Edit Chart" window, clicked save without making any changes, and the problem was resolved. I didn’t modify anything else, as they were already migrated.
> Also, what version are you running now, is it a 4.x variant? Is there any remaining issue after overwriting the charts? Trying to figure out how to reproduce this issue or what we can do to move it forward.
Upgraded from 2.1.1 to 4.1.1, but the issue seems to occur in all versions after 3.0.0, as I've tested them and encountered the same problem. There is no issue left after doing this.
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Performance issues after migration from 2.1.1 causing by pivot tables [superset]
Posted by "iercan (via GitHub)" <gi...@apache.org>.
iercan commented on issue #31799:
URL: https://github.com/apache/superset/issues/31799#issuecomment-2591916631
@rusackas This issue had been blocking our upgrade since 2.1.1. Fortunately, we found the cause! I opened this issue to share a workaround and assist others facing the same problem. It might not be worth the effort to solve, so it may be better to close it.
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [I] Performance issues after migration from 2.1.1 causing by pivot tables [superset]
Posted by "iercan (via GitHub)" <gi...@apache.org>.
iercan closed issue #31799: Performance issues after migration from 2.1.1 causing by pivot tables
URL: https://github.com/apache/superset/issues/31799
--
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: notifications-unsubscribe@superset.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org