Maintainer page optimization #122
Labels
Component: webapp
repology-webapp, repology web application
Effort: intermediate
A class or a huge function needs to be written
Priority: someday
Normal priority
Topic: performance
Both optimizations and perf monitoring
Type: refactoring
Internal improvements which do not change behavior
P99 is above 1sec, should be optimized.
It's already known though that similar maintainers query is rather slow since it needs to process a lot of
maintainer_metapackages
(to get all maintainers with intersecting projects list), then fetch maintainer info for all of these.Real optimization would need prepared data, such as
maintainer_id/project_id/num_maintainer_projects
table which is smaller and does not require join withmaintainers
, or similar maintainers percomputed totally offline.For now, reducing
maintainer_metapackages
should also help, such as by dropping unneeded maintainers (#121), and giving more memory to the database, asmaintainer_metapackages
is quite hot and should be well cached.The text was updated successfully, but these errors were encountered: