Symfony Profiler

{
    "@context": [
        "https:\/\/join-lemmy.org\/context.json",
        "https:\/\/www.w3.org\/ns\/activitystreams"
    ],
    "actor": "https:\/\/lemmy.world\/c\/selfhosted",
    "to": [
        "https:\/\/www.w3.org\/ns\/activitystreams#Public"
    ],
    "object": {
        "id": "https:\/\/midwest.social\/activities\/create\/0b22c947-7164-454b-b5bd-2154e6cd1fca",
        "actor": "https:\/\/midwest.social\/u\/sxan",
        "@context": [
            "https:\/\/join-lemmy.org\/context.json",
            "https:\/\/www.w3.org\/ns\/activitystreams"
        ],
        "to": [
            "https:\/\/www.w3.org\/ns\/activitystreams#Public"
        ],
        "object": {
            "type": "Note",
            "id": "https:\/\/midwest.social\/comment\/16824085",
            "attributedTo": "https:\/\/midwest.social\/u\/sxan",
            "to": [
                "https:\/\/www.w3.org\/ns\/activitystreams#Public"
            ],
            "cc": [
                "https:\/\/lemmy.world\/c\/selfhosted",
                "https:\/\/sh.itjust.works\/u\/traches"
            ],
            "content": "<p>The densities I\u2019m seeing on M-Discs - 100GB, $5 per, a couple years ago - seemed acceptable to me. $50 for a TB? How big is your archive? Mine still fits in a 2TB disk.<\/p>\n<blockquote>\n<p>Copying files directly would work, but my library is real big and that sounds tedious.<\/p>\n<\/blockquote>\n<p>I mean, putting it in an archive isn\u2019t going to make it any smaller. Compression on even lossless compressed images doesn\u2019t often help.<\/p>\n<p>And we\u2019re talking about 100GB discs. Is squeezing that last 10MB out of the disk by splitting an image across two disks worth it?<\/p>\n<p>The metadata is a different matter. I\u2019d have to think about how to handle the sidecar data\u2026 but <em>that<\/em> you could almost keep on a DVD-RW, because there\u2019s no way that\u2019s going to be anywhere near as large as the photos themselves. Is your photo editor DB bigger than 4GB?<\/p>\n<p>I never change the originals. When I tag and edit, that information is kept separate from the source images - so I never have multiple versions of pictures, unless I export them for printing, or something, and those are ephemeral and can be re-exported by the editor with the original and the sidecar. Music, and photos, I always keep the originals isolated from the application.<\/p>\n<p>This is good, though; it\u2019s helping me clarify how I want to archive this stuff. Right now mine is just backed up on multiple disks and once in B2, but I\u2019ve been thinking about how to archive for long term storage.<\/p>\n<p>I think in going to go the M-Disc route, with sidecar data on SSD and backed up to BluRay RW. The trick will be letting DarkTable know that the source images are on different media, but I\u2019m pretty sure I saw an option for that. For sure, we\u2019re not the first people to approach this problem.<\/p>\n<p>The whole static binary thing - I\u2019m going that route with an encrypted share for financial and account info, in case I die, but that\u2019s another topic.<\/p>\n",
            "inReplyTo": "https:\/\/sh.itjust.works\/comment\/18045635",
            "mediaType": "text\/html",
            "source": {
                "content": "The densities I'm seeing on M-Discs - 100GB, $5 per, a couple years ago - seemed acceptable to me. $50 for a TB? How big is your archive? Mine still fits in a 2TB disk.\n\n> Copying files directly would work, but my library is real big and that sounds tedious.\n\nI mean, putting it in an archive isn't going to make it any smaller. Compression on even lossless compressed images doesn't often help.\n\nAnd we're talking about 100GB discs. Is squeezing that last 10MB out of the disk by splitting an image across two disks worth it?\n\nThe metadata is a different matter. I'd have to think about how to handle the sidecar data... but _that_ you could almost keep on a DVD-RW, because there's no way that's going to be anywhere near as large as the photos themselves. Is your photo editor DB bigger than 4GB?\n\nI never change the originals. When I tag and edit, that information is kept separate from the source images - so I never have multiple versions of pictures, unless I export them for printing, or something, and those are ephemeral and can be re-exported by the editor with the original and the sidecar. Music, and photos, I always keep the originals isolated from the application.\n\nThis is good, though; it's helping me clarify how I want to archive this stuff. Right now mine is just backed up on multiple disks and once in B2, but I've been thinking about how to archive for long term storage.\n\nI think in going to go the M-Disc route, with sidecar data on SSD and backed up to BluRay RW. The trick will be letting DarkTable know that the source images are on different media, but I'm pretty sure I saw an option for that. For sure, we're not the first people to approach this problem.\n\nThe whole static binary thing - I'm going that route with an encrypted share for financial and account info, in case I die, but that's another topic.",
                "mediaType": "text\/markdown"
            },
            "published": "2025-04-19T01:51:31.022156Z",
            "tag": [
                {
                    "href": "https:\/\/sh.itjust.works\/u\/traches",
                    "name": "@traches@sh.itjust.works",
                    "type": "Mention"
                }
            ],
            "distinguished": false,
            "language": {
                "identifier": "en",
                "name": "English"
            },
            "audience": "https:\/\/lemmy.world\/c\/selfhosted",
            "attachment": []
        },
        "cc": [
            "https:\/\/lemmy.world\/c\/selfhosted",
            "https:\/\/sh.itjust.works\/u\/traches"
        ],
        "tag": [
            {
                "href": "https:\/\/sh.itjust.works\/u\/traches",
                "name": "@traches@sh.itjust.works",
                "type": "Mention"
            }
        ],
        "type": "Create",
        "audience": "https:\/\/lemmy.world\/c\/selfhosted"
    },
    "cc": [
        "https:\/\/lemmy.world\/c\/selfhosted\/followers"
    ],
    "type": "Announce",
    "id": "https:\/\/lemmy.world\/activities\/announce\/create\/4788e8bb-3ea6-44a9-8e98-6635f771d143"
}

{"@context":["https://join-lemmy.org/context.json","https://www.w3.org/ns/activitystreams"],"actor":"https://lemmy.world/c/selfhosted","to":["https://www.w3.org/ns/activitystreams#Public"],"object":{"id":"https://midwest.social/activities/create/0b22c947-7164-454b-b5bd-2154e6cd1fca","actor":"https://midwest.social/u/sxan","@context":["https://join-lemmy.org/context.json","https://www.w3.org/ns/activitystreams"],"to":["https://www.w3.org/ns/activitystreams#Public"],"object":{"type":"Note","id":"https://midwest.social/comment/16824085","attributedTo":"https://midwest.social/u/sxan","to":["https://www.w3.org/ns/activitystreams#Public"],"cc":["https://lemmy.world/c/selfhosted","https://sh.itjust.works/u/traches"],"content":"<p>The densities I’m seeing on M-Discs - 100GB, $5 per, a couple years ago - seemed acceptable to me. $50 for a TB? How big is your archive? Mine still fits in a 2TB disk.</p>\n<blockquote>\n<p>Copying files directly would work, but my library is real big and that sounds tedious.</p>\n</blockquote>\n<p>I mean, putting it in an archive isn’t going to make it any smaller. Compression on even lossless compressed images doesn’t often help.</p>\n<p>And we’re talking about 100GB discs. Is squeezing that last 10MB out of the disk by splitting an image across two disks worth it?</p>\n<p>The metadata is a different matter. I’d have to think about how to handle the sidecar data… but <em>that</em> you could almost keep on a DVD-RW, because there’s no way that’s going to be anywhere near as large as the photos themselves. Is your photo editor DB bigger than 4GB?</p>\n<p>I never change the originals. When I tag and edit, that information is kept separate from the source images - so I never have multiple versions of pictures, unless I export them for printing, or something, and those are ephemeral and can be re-exported by the editor with the original and the sidecar. Music, and photos, I always keep the originals isolated from the application.</p>\n<p>This is good, though; it’s helping me clarify how I want to archive this stuff. Right now mine is just backed up on multiple disks and once in B2, but I’ve been thinking about how to archive for long term storage.</p>\n<p>I think in going to go the M-Disc route, with sidecar data on SSD and backed up to BluRay RW. The trick will be letting DarkTable know that the source images are on different media, but I’m pretty sure I saw an option for that. For sure, we’re not the first people to approach this problem.</p>\n<p>The whole static binary thing - I’m going that route with an encrypted share for financial and account info, in case I die, but that’s another topic.</p>\n","inReplyTo":"https://sh.itjust.works/comment/18045635","mediaType":"text/html","source":{"content":"The densities I'm seeing on M-Discs - 100GB, $5 per, a couple years ago - seemed acceptable to me. $50 for a TB? How big is your archive? Mine still fits in a 2TB disk.\n\n> Copying files directly would work, but my library is real big and that sounds tedious.\n\nI mean, putting it in an archive isn't going to make it any smaller. Compression on even lossless compressed images doesn't often help.\n\nAnd we're talking about 100GB discs. Is squeezing that last 10MB out of the disk by splitting an image across two disks worth it?\n\nThe metadata is a different matter. I'd have to think about how to handle the sidecar data... but _that_ you could almost keep on a DVD-RW, because there's no way that's going to be anywhere near as large as the photos themselves. Is your photo editor DB bigger than 4GB?\n\nI never change the originals. When I tag and edit, that information is kept separate from the source images - so I never have multiple versions of pictures, unless I export them for printing, or something, and those are ephemeral and can be re-exported by the editor with the original and the sidecar. Music, and photos, I always keep the originals isolated from the application.\n\nThis is good, though; it's helping me clarify how I want to archive this stuff. Right now mine is just backed up on multiple disks and once in B2, but I've been thinking about how to archive for long term storage.\n\nI think in going to go the M-Disc route, with sidecar data on SSD and backed up to BluRay RW. The trick will be letting DarkTable know that the source images are on different media, but I'm pretty sure I saw an option for that. For sure, we're not the first people to approach this problem.\n\nThe whole static binary thing - I'm going that route with an encrypted share for financial and account info, in case I die, but that's another topic.","mediaType":"text/markdown"},"published":"2025-04-19T01:51:31.022156Z","tag":[{"href":"https://sh.itjust.works/u/traches","name":"@traches@sh.itjust.works","type":"Mention"}],"distinguished":false,"language":{"identifier":"en","name":"English"},"audience":"https://lemmy.world/c/selfhosted","attachment":[]},"cc":["https://lemmy.world/c/selfhosted","https://sh.itjust.works/u/traches"],"tag":[{"href":"https://sh.itjust.works/u/traches","name":"@traches@sh.itjust.works","type":"Mention"}],"type":"Create","audience":"https://lemmy.world/c/selfhosted"},"cc":["https://lemmy.world/c/selfhosted/followers"],"type":"Announce","id":"https://lemmy.world/activities/announce/create/4788e8bb-3ea6-44a9-8e98-6635f771d143"}