hasura / hasura/graphql-engine

Databases with a large number of partitions (100+) causes the console to freeze

Open
#9,509 3 comments 1 reaction 1 assignee Claimed by @vijayprasanna13 View on GitHub
a/performance c/console estimate/L
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

### Version Information

Server Version: latest oss

### Environment

OSS/Cloud/EE

### What is the current behaviour?

Database schemas with lot of partitions causes the console UI to become unresponsive and throw alerts.

### What is the expected behaviour?

The `Manage Database` section of the console should work as expected and list the untracked tables.

### How to reproduce the issue?

1. Track a database with 100+ partitions.
2. Navigate to the `Manage Database` section (click on the database name on the nav tree).
3. The UI becomes unresponsive while trying to load the list of untracked tables.

### Any possible solutions/workarounds you're aware of?

1. Hide the partitions while listing untracked tables in `Manage Database` section.
2. Add pagination to the list of tables.

### Keywords
console, performance, postgres

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.