Client participation in the federated computation rounds

Issue

I am building a federated learning model using Tensorflow Federated.
Based on what I have read in the tutorials and papers, I understood that the state-of-the-art method (FedAvg) is working by selecting a random subset of clients at each round.

My concern is:

  • I am having a small number of clients. Totally I have 8 clients, I select 6 clients for training and I kept 2 for testing.
  • All of the data are provided on my local device, so I am using the TFF as the simulation environment.
  • If I use all of the 6 clients in all of the rounds during federated communication rounds, would this be a wrong execution of the FedAvg method?
  • Note that I am planning also to use the same experiment used in this paper. That aims to use different server optimization methods and compare their performance. So, would (all clients participating procedure) works here or not?

Thanks in advance

Solution

This is certainly a valid application of FedAvg and the variants proposed in the linked paper, though one that is only studied empirically in a subset of the literature. On the other hand, many theoretical analyses of FedAvg assume a similar situation to the one you’re describing; at the bottom of page 4 of that linked paper, you will see that the analysis is performed in this so-called ‘full participation’ regime, where every client participates on every round.

Often the setting you describe is called ‘cross silo’; see, e.g., section 7.5 of Advances and Open Problems in Federated Learning, which will also contain many useful pointers for the cross-silo literature.

Finally, depending on the application, consider that it may be more natural to literally train on all clients, reserving portions of each clients’ data for validation and test. Questions around natural partitions of data to model the ‘setting we care about’ are often thorny in the federated setting.

Answered By – Keith Rush

This Answer collected from stackoverflow, is licensed under cc by-sa 2.5 , cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply

(*) Required, Your email will not be published