Could Git be smarter about object reuse?

Hello, I'm not entirely sure about the details of pushing, but I've noticed that basically it just uploads every object the server might need in relationship to that commit which can be a huge amount of data and sometimes even exceed the server-defined request timeout, causing the push to fail.

It's especially annoying because I know the server already has basically all the blobs needed and hence would only need to receive the commit and tree objects.

Are there any hidden flags or future cosiderations that could be made to reduce the bandwidth needed for such pushes?

-- Sainan