Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
High CPU usage after upgrade to 0.26.1 #6209
Running on ECS (using docker image), connecting to Redshift.
CPU spikes at 45 past the hour, and reduces at ~20 past the hour. Restarting the task doesn't seem to do much, for now I've increased CPU allocation, but ideally would like to resolve any problem.
Not sure if this is related to the deadlock issue raised in another issue. If it is, feel free to close.
Let me know if you need anymore specific information.
Yeah, it happens to me too. The process consumes 100% of CPU and metabase completely freezes. One can't access the interface, it keeps loading forever. So I have to restart the process.
When this happens, the log does not give any clue on the cause, it just show some errors from Slack integration (but this is turned off in the admin panel) and stops logging until I restart the process.
I've been digging more into metabase's settings and it seems like turning off hourly scanning for filter values drastically reduces the peaks hourly. I'm guessing the remaining smaller peaks are related to the database syncing that happens.
I did initially tie some of the improvement to xrays, so I'm going to switch those back on and confirm that wasn't actually affecting anything.
Same issues, after upgrade Metabase from 0.25 to the latest 0.27.2, DATABASE SYNCING
DATABASE SYNCING take around 1hr and around 30% of SQL CPU (I've setup one time Daily).
DATABASE SYNCING should be "lightweight process", but is very (too) high to only checks updates to database schema.