assetbundles and server request load

Hi,

I am in the process of designing the assetbundles portion of my prototype and would like to know if too much client accessing low size files would impose a too big charge against bigger files.

For example, I have multiple wall indexes of different sets to create a room. I am faced with the problem of thinking about loading speed, is an assetbundle with only one wall of a given set is a better strategy than having all walls of a set in one bundle. at the moment, the walls are about 4k each in assetbundle. I suppose a full set would be between 50-150k for 25 wall indexes, depending on the geometry of the wall sets.

Any thoughts on the better course ? would loading async simply resolve a loading issue with a bigger file. The problem that rise is that when a player has customized his room with multiple walls from different sets, it just doesn't make sense to load 7x 150 k...

If the player has a 20x20 room with a possibility of 400 wall tiles, it could still take some time to load. I know putting a wall on all tiles is silly, but it still important to think everything out at the beginning.