Symfony Profiler

{
    "@context": [
        "https:\/\/join-lemmy.org\/context.json",
        "https:\/\/www.w3.org\/ns\/activitystreams"
    ],
    "actor": "https:\/\/lemmy.ml\/c\/announcements",
    "to": [
        "https:\/\/www.w3.org\/ns\/activitystreams#Public"
    ],
    "object": {
        "id": "https:\/\/lemmy.ml\/activities\/update\/f86e4411-26da-4a33-a666-ca5b0d9ec410",
        "actor": "https:\/\/lemmy.ml\/u\/dessalines",
        "to": [
            "https:\/\/www.w3.org\/ns\/activitystreams#Public"
        ],
        "object": {
            "type": "Note",
            "id": "https:\/\/lemmy.ml\/comment\/17538468",
            "attributedTo": "https:\/\/lemmy.ml\/u\/dessalines",
            "to": [
                "https:\/\/www.w3.org\/ns\/activitystreams#Public"
            ],
            "cc": [
                "https:\/\/lemmy.ml\/c\/announcements",
                "https:\/\/lemmy.ml\/u\/Transform2942"
            ],
            "content": "<p>The <a href=\"https:\/\/github.com\/LemmyNet\/lemmy\/blob\/main\/crates\/db_views\/src\/post\/post_view.rs\" rel=\"nofollow\">post list query<\/a> is by far the worst offender. It needs to filter, sort, cursor paginate, and join to many tables, and indexes are hard to follow and keep up with.<\/p>\n<p>What\u2019s more is that the problems only surface with lots of historical data, meaning we can only really test the query plans with a fully populated DB.<\/p>\n<p>All this requires running lemmy locally, and inspecting the postgres query durations. We really need proper test suites (<a href=\"https:\/\/github.com\/LemmyNet\/lemmy\/blob\/main\/crates\/db_perf\/src\/main.rs\" rel=\"nofollow\">lemmy DB perf is one example<\/a>) that can stress-test production data also.<\/p>\n<p>Here is one historical issue:<\/p>\n<ul>\n<li><a href=\"https:\/\/github.com\/LemmyNet\/lemmy\/issues\/2877\">github.com\/LemmyNet\/lemmy\/issues\/2877<\/a><\/li>\n<\/ul>\n<p>I\u2019d very much appreciate any help.<\/p>\n",
            "inReplyTo": "https:\/\/lemmy.ml\/comment\/17538040",
            "mediaType": "text\/html",
            "source": {
                "content": "The [post list query](https:\/\/github.com\/LemmyNet\/lemmy\/blob\/main\/crates\/db_views\/src\/post\/post_view.rs) is by far the worst offender. It needs to filter, sort, cursor paginate, and join to many tables, and indexes are hard to follow and keep up with. \n\nWhat's more is that the problems only surface with lots of historical data, meaning we can only really test the query plans with a fully populated DB. \n\nAll this requires running lemmy locally, and inspecting the postgres query durations. We really need proper test suites ([lemmy DB perf is one example](https:\/\/github.com\/LemmyNet\/lemmy\/blob\/main\/crates\/db_perf\/src\/main.rs)) that can stress-test production data also.\n\nHere is one historical issue:\n\n- https:\/\/github.com\/LemmyNet\/lemmy\/issues\/2877\n\nI'd very much appreciate any help.",
                "mediaType": "text\/markdown"
            },
            "published": "2025-03-26T15:57:43.777281Z",
            "updated": "2025-03-26T15:58:15.073256Z",
            "tag": [
                {
                    "href": "https:\/\/lemmy.ml\/u\/Transform2942",
                    "name": "@Transform2942@lemmy.ml",
                    "type": "Mention"
                }
            ],
            "distinguished": false,
            "language": {
                "identifier": "en",
                "name": "English"
            },
            "audience": "https:\/\/lemmy.ml\/c\/announcements",
            "attachment": []
        },
        "cc": [
            "https:\/\/lemmy.ml\/c\/announcements",
            "https:\/\/lemmy.ml\/u\/Transform2942"
        ],
        "tag": [
            {
                "href": "https:\/\/lemmy.ml\/u\/Transform2942",
                "name": "@Transform2942@lemmy.ml",
                "type": "Mention"
            }
        ],
        "type": "Update",
        "audience": "https:\/\/lemmy.ml\/c\/announcements"
    },
    "cc": [
        "https:\/\/lemmy.ml\/c\/announcements\/followers"
    ],
    "type": "Announce",
    "id": "https:\/\/lemmy.ml\/activities\/announce\/update\/05104a6f-4a31-45b1-ab4a-cfdcb8b76c14"
}

{"@context":["https://join-lemmy.org/context.json","https://www.w3.org/ns/activitystreams"],"actor":"https://lemmy.ml/c/announcements","to":["https://www.w3.org/ns/activitystreams#Public"],"object":{"id":"https://lemmy.ml/activities/update/f86e4411-26da-4a33-a666-ca5b0d9ec410","actor":"https://lemmy.ml/u/dessalines","to":["https://www.w3.org/ns/activitystreams#Public"],"object":{"type":"Note","id":"https://lemmy.ml/comment/17538468","attributedTo":"https://lemmy.ml/u/dessalines","to":["https://www.w3.org/ns/activitystreams#Public"],"cc":["https://lemmy.ml/c/announcements","https://lemmy.ml/u/Transform2942"],"content":"<p>The <a href=\"https://github.com/LemmyNet/lemmy/blob/main/crates/db_views/src/post/post_view.rs\" rel=\"nofollow\">post list query</a> is by far the worst offender. It needs to filter, sort, cursor paginate, and join to many tables, and indexes are hard to follow and keep up with.</p>\n<p>What’s more is that the problems only surface with lots of historical data, meaning we can only really test the query plans with a fully populated DB.</p>\n<p>All this requires running lemmy locally, and inspecting the postgres query durations. We really need proper test suites (<a href=\"https://github.com/LemmyNet/lemmy/blob/main/crates/db_perf/src/main.rs\" rel=\"nofollow\">lemmy DB perf is one example</a>) that can stress-test production data also.</p>\n<p>Here is one historical issue:</p>\n<ul>\n<li><a href=\"https://github.com/LemmyNet/lemmy/issues/2877\">github.com/LemmyNet/lemmy/issues/2877</a></li>\n</ul>\n<p>I’d very much appreciate any help.</p>\n","inReplyTo":"https://lemmy.ml/comment/17538040","mediaType":"text/html","source":{"content":"The [post list query](https://github.com/LemmyNet/lemmy/blob/main/crates/db_views/src/post/post_view.rs) is by far the worst offender. It needs to filter, sort, cursor paginate, and join to many tables, and indexes are hard to follow and keep up with. \n\nWhat's more is that the problems only surface with lots of historical data, meaning we can only really test the query plans with a fully populated DB. \n\nAll this requires running lemmy locally, and inspecting the postgres query durations. We really need proper test suites ([lemmy DB perf is one example](https://github.com/LemmyNet/lemmy/blob/main/crates/db_perf/src/main.rs)) that can stress-test production data also.\n\nHere is one historical issue:\n\n- https://github.com/LemmyNet/lemmy/issues/2877\n\nI'd very much appreciate any help.","mediaType":"text/markdown"},"published":"2025-03-26T15:57:43.777281Z","updated":"2025-03-26T15:58:15.073256Z","tag":[{"href":"https://lemmy.ml/u/Transform2942","name":"@Transform2942@lemmy.ml","type":"Mention"}],"distinguished":false,"language":{"identifier":"en","name":"English"},"audience":"https://lemmy.ml/c/announcements","attachment":[]},"cc":["https://lemmy.ml/c/announcements","https://lemmy.ml/u/Transform2942"],"tag":[{"href":"https://lemmy.ml/u/Transform2942","name":"@Transform2942@lemmy.ml","type":"Mention"}],"type":"Update","audience":"https://lemmy.ml/c/announcements"},"cc":["https://lemmy.ml/c/announcements/followers"],"type":"Announce","id":"https://lemmy.ml/activities/announce/update/05104a6f-4a31-45b1-ab4a-cfdcb8b76c14"}