[SERVER-74322] consider removing thin archive caching Created: 23/Feb/23  Updated: 23/Feb/23  Resolved: 23/Feb/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Daniel Moody Assignee: [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Server Development Platform
Participants:

 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.



 Comments   
Comment by Daniel Moody [ 23/Feb/23 ]

I looked into it, and a transfer time is on the order of 10s of milliseconds vs 1-2 seconds to rebuild locally. There is around 1000 libs so after dividing by the j for a rough estimate of total time delay for the build its on the order of 10s of seconds. I think we should maintain caching the thin_archives so I will close this ticket as wont do.

Generated at Thu Feb 08 06:27:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.