publiclab/mapknitter

Define a max number of image versions to store / gallery view slowness

Open

#1,167 opened on Dec 19, 2019

View on GitHubContributor guide
 (11 comments) (0 reactions) (0 assignees)Ruby (203 forks)auto 404
help wantedpriorityrefactoringruby

Repository metrics

Stars
 (274 stars)
PR merge metrics
 (PR metrics pending)

Description

Quoting @jywarren : "come up with a rubric for max # of versions created PER PERIOD" (...) this would require some planning and policy discussion.

Not sure how this relates to the features but the thing is that paper-trail gem seems to be related to slowness and it suggests for performance to "limit the number of versions".

From a DBA point of view, currently our heaviest table is "warpables" with 268723 records. Can we do something to reduce or optimize this? Thanks!

What happened just before the problem occurred

Relevant URLs

https://

PublicLab.org username

(to help reproduce the issue)

Browser, version, and operating system

For bug reports, fill out the above template; for feature requests, you can delete the template.

Contributor guide

Research direction
Investigate the paper trail gem usage and database query patterns for the warpables table to identify performance bottlenecks and propose a policy for limiting image versions.
Tech stack
ruby
Domain
backendperformance
Issue type
Performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40