Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-74322

consider removing thin archive caching

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Won't Do
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Server Development Platform

    Description

      We should look at the time difference between caching and transferring the thin_archives vs just rebuilding them each time.

       

      even though we switched away from caching linked bins in https://jira.mongodb.org/browse/SERVER-74278, thin archives are still cached: https://jira.mongodb.org/browse/SERVER-33958
      thin archives are .a files which just use references to object files, so they are very small. I wonder if the extra number of small files we are transferring is worth what ever savings we get from caching. I would be surprised if there was any significant diff in time between transfer a thin archive vs rebuilding a thin archive.

      Attachments

        Activity

          People

            backlog-server-devplatform [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive)
            daniel.moody@mongodb.com Daniel Moody
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: