alamb commented on PR #542: URL: https://github.com/apache/arrow-rs-object-store/pull/542#issuecomment-3512706352
> It's true, but I figured the read:write ratio is SO high (basically, 100% reads within the TTL window), that I'd like to avoid the (relatively) higher cost of an RwLock for the majority case. Would it be useful to illustrate this with a benchmark, or are you categorically against adding new dependencies? I think a super read heavy workload will work well with `RWLock` > Would it be useful to illustrate this with a benchmark, or are you categorically against adding new dependencies? In my mind, the burden of evidence is much higher to add a new dependency. I know it sounds somewhat like a curmudgeon, but each new dependency adds some small (but real) additional maintenance overhead (and downstream work). Unless there is compelling demonstrated value to add a new dependency, we try and avoid it. Also, there are very few contributions *removing* dependencies for some reason 😆 so once we add one we are typically stuck with them. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
