Opened 8 years ago

Closed 7 years ago

#3889 closed defect (wontfix)

Analyze metrics database configuration for possible performance bottleneck

Reported by: karsten Owned by: karsten
Priority: Medium Milestone:
Component: Metrics/Website Version:
Severity: Keywords:
Cc: Sebastian, phobos Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

The metrics database on yatei is much slower than a freshly set up database on Sebastian's laptop. To some extent this is understandable, because things deteriorate over time. But relay-search queries that take seconds or less on Sebastian's laptop shouldn't take minutes to complete on yatei. We should take a look if we can tweak yatei's database configuration to remove some bottlenecks.

Possible candidates for tweaks are auto-vacuuming intervals, indexes, backups, etc.

How can we compare database configurations? Can we put up yatei's PostgreSQL configuration anywhere public? Also, what PostgreSQL statistics should we compare?

Child Tickets

Change History (3)

comment:1 Changed 8 years ago by Sebastian

For the record, here are my laptop specs: i7 quadcore 2.3ghz, 8GB ram, 128GB SSD. I only set up the one big table with all descriptors ever in it, and ran the queries we run on metrics.

comment:2 Changed 8 years ago by karsten

When we tried this out on Sebastian's laptop, we dumped the statusentry table from yatei and imported it there. \dt+ says this table is 34 GB large as of today.

comment:3 Changed 7 years ago by karsten

Resolution: wontfix
Status: newclosed

We solved the problem with relay searches taking minutes by partitioning the database table. Closing this ticket.

Note: See TracTickets for help on using tickets.